https://bugzilla.novell.com/show_bug.cgi?id=331002#c28
--- Comment #28 from Kay Sievers 2007-10-25 16:46:39 MST ---
Properly written services do not return from forking until they are ready to
use. If D-Bus has problems here, we should fix the daemon itself, and not try
to ensure anything in the init script.
I guess, it seemed to work for you because D-Bus without internal fork() is
just that bit faster, that it is initialized before the script terminates. But
it's still unreliable and unpredictable, and letting D-Bus itself block the
init script execution is the right solution.
If external tools (startproc, init replacements) should do the
forking/supervising/babysitting of a system service, the services itself must
provide a signaling method when its initialization has finished, otherwise the
forking process will never be able to guarantee the requirements for the
dependent services.
Startproc (in its current async behavior) can not be used for any service that
has dependencies. Even for a complete serialized startup, it may cause problems
when services are initializing in the background, while later services depend
on it.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.