I upgraded from SysVinit-2.78-19 to SysVinit-2.79-1. Now, when I reboot my
machine, atalkd gets a suspend signal at some point during the reboot
process, i.e., after I reboot, atalkd is in state "T" according to ps, and
none of the other processes that should have been started during "service
atalk start" are running. (Atalkd is part of the netatalk package from
Note that the atalk startup script is special in that it starts up atalkd,
etc. in the background because they're slow to start up.
Reverting to SysVinit-2.78-19 made the problem go away, so there's cearlly
something fishy with SysVinit, regardless of whether you're continuing to
support netatalk (and even if you aren't, it's a useful test case for
reproducing the problem in SysVinit).
It may be relevant that atalk is started near the end of the boot process,
so it isn't finished launching all the atalk processes before the boot
This is still broken in 2.79-2.
This got fixed with 2.84-x, yes?
Yes, it appears to be fixed in 2.84-5, although I can't say exactly when it was
fixed since I had modified my atalk configuration to start the daemons in the
foreground to avoid this problem (i.e., I don't know whether it's fixed in Limbo).
Yeah, 2.79 showed various brokenness; that's why we didn't end up shipping it.
Apologies for the delay.