fs.existsSync() seems to fail on symlink (or relative path?)

[pldelattre]

service fails with exception 'ExpectedTlsCert' (ln-service/lightning/lightning_daemon.js line 50) if i set

export LNSERVICE_LND_DIR='~/.lnd/'

However it starts without issue if I set

export LNSERVICE_LND_DIR='/home/pi/data/ext4/LightningData'

Knowing that my ~/.lnd/ is a symlink to /home/pi/data/ext4/LightningData

pi@raspberrypi:~/ln-service $ ls -l ~/.lnd lrwxrwxrwx 1 pi pi 33 May 22 11:44 /home/pi/.lnd -> /home/pi/data/ext4/LightningData/

Not sure to understand why.

[alexbosworth]

I didn’t test it with symlinks, possible it doesn’t support that in its check. Is it a real workaround to just use the direct path or that also causes problems?

[pldelattre]

It is a real workaround.

On Wed 23 May 2018 at 15:52, Alex Bosworth [email protected] wrote:

I didn’t test it with symlinks, possible it doesn’t support that in its check. Is it a real workaround to just use the direct path or that also causes problems?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/alexbosworth/ln-service/issues/25#issuecomment-391354790, or mute the thread https://github.com/notifications/unsubscribe-auth/AS0TwPTKyG_-wVpb_7Pd8oCFm2vd8TU9ks5t1WmwgaJpZM4UKIVm .

[litch]

I experienced this also in linux (ubuntu 18.04).

[dennisreimann]

Just checked: existsSync works with symlinks and I verified the checks in local_lnd.js also work with a symlinked path as value for LNSERVICE_LND_DIR.