> > Maybe you could be clearer because scripting is almost boundless. > > There is no way to specify in DAEMONS that syslog-ng and dbus should be > started in parallel, and only when they are both up and running should > network manager be started. > Personally I don't care about shaving a second or two but the simplest config change could be. DAEMONS="syslog-ng(3), dbus(3), network-manager(4)" > > > that depend on them having completely > > > launched. > > > > In the interests of learning for my scripts and hopefully without > > leading the witnesses who may badger Tom? I'm interested to know how > > systemd knows universally that a service is "completely launched" > > ignoring that daemons themselves don't always know? > > A well written sysv daemon should only double fork once it is 'ready'. > initscripts relies on this behaviour already (that is how we know when to > start the 'next' daemon from the DAEMONS array). Systemd can either use > this mechanism (Type= forking) or one of several other ones. That said, > there its no magic: if the daemon does not know, then systemd does not know. Thanks -- ________________________________________________________ Why not do something good every day and install BOINC. ________________________________________________________
