On Tue, Mar 07, 2023 at 03:22:53PM +0000, Rainer Weikusat via Dng wrote: > > Traditionally, this type of daemon would remain in foreground until it
> > was functional, and then doublefork itself, at which time sysvinit
> > would run the next daemon.
> That's an urban myth. There is no such convention and "daemon readiness"
> isn't a well-defined concept. Current implementations of SysV-RC start
> jobs in parallell (and have for some time).
The traditional symlinks and sequence numbers are still there, though.
What purpose do they serve, then? At what point does rc proceed from
handling /etc/rc2.d/S02unbound to /etc/rc2.d/S03cron ? (or is there such
a distinct point at all?)
This message was posted to the following mailing lists: