Hi, Lars Rustand <[email protected]> skribis:
> So, I figured this out. It had nothing to do with networking even though > it looked like it. The problem was that I had cargo cult-copied a > #:pid-file parameter from another service, believing that this was just > a path were Shepherd could create a pid-file for the service, but > Shepherd was in fact expecting the program to create the pid-file. So > when the program did not create this pid-file then Shepherd killed the > program. > > So the original bug I reported is in fact not a bug at all and can be > closed. However, the error handling in Shepherd could be improved in > order to make it more clear what is happening. Good that you found the issue! I improved logging for this particular case as a result of this report: https://git.savannah.gnu.org/cgit/shepherd.git/commit/?id=ace4a3b2dba43b826640d5c1ca970f9040d27416 Thanks for reporting it, Ludo’.
