Sles 11 (SuSE) has logger in /bin/ not in /usr/bin/.
andabata opened this issue · comments
And gives an error:
Apr 11 11:55:50 hotel gocryptfs[52806]: redirectStdFds: could not start logger: fork/exec /usr/bin/logger: no such file or directory
Thanks for the report! Patch follows shortly...
just to chime in - please don't hardcode paths, for example I'm on NixOS and logger lives in /run/current-system/sw/bin/logger
The reason for the hardcoded paths was that the PATH environment variable is not set when we are mounted from /etc/fstab. However, commit 10212d7 should handle that case, and I think I can drop the hardcoded paths.
This commit appears to already be in v1.6_2018-10-17, that's the version I'm running. However, I'm forced to sed -i 's|"/bin/logger"|&, "/run/current-system/sw/bin/logger"|' daemonize.go to get it to run.
Same thing goes for path, some distros are really bizarre.
May I suggest a command line option that can override the few places gocryptfs has hardcoded paths, unless it's given it should stick to defaults of sane /bin /usr/bin etc... But for those of us on eclectic systems it would help a lot to not have to patch sources.
Many thanks!
@voobscout Fixed in d882ed4 . No command line options neccessary, just PATH should be set to the right value for the distro.
Many thanks! that certainly makes it easier to package gocryptfs!