On 07/12/2011 10:42 AM, Reindl Harald wrote: > in the real world processes like mysqld which are multi-threaded > you can get a successfull return-code while the process is > finishing his tasks which is my biggest problem with systemd > > the process itself knows that he is running fine, finish his > own init and giving a success code but is not ready for > connections in the same moment and if another process is > fired up which wants to speak with it this one will fail You're describing a bug. Exiting the original process before daemonization is finished, before the sockets are listening, or before the pidfile is written, is a wrong way to start a daemon. It's a bug regardless of the init system used (SysV initscript, systemd, ...). Michal -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
