Lars Rustand <rustand.l...@gmail.com> writes:
> Hello, I have created two very simple shepherd services for two > different mail programs (offlineimap and davmail). Both of the programs > are able to run without problem when ran from the commandline, but both > of them fail with networking related errors when I try to run them as > shepherd services. ... > They both seem to fail when opening an *outgoing* socket, but davmail > seems to be able to start *listening* on several ports just fine. 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.
