Hi, Carlo Zancanaro <ca...@zancanaro.id.au> skribis:
> Yeah, I saw that note in the documentation. I used to have > > (action 'shepherd 'daemonize) > > as the first line in ~/.config/shepherd/init.scm. Is there some other > way that I was supposed to do that? No, I think that should work. > With that line in place, Shepherd will leave behind a process every > time I stop/start a service. > > I have attached an example init.scm that does this for me. If I start: > > shepherd -c init.scm > > and then run: > > herd stop sleep > herd start sleep > herd stop sleep > herd start sleep > herd stop sleep > > then I will have three zombie sleep processes underneath my Shepherd > process. (If the service were respawnable then it also would fail to > restart the service.) Could you run shepherd in “strace -f” and see where the SIGCHLD signals go? Thanks, Ludo’.