On Mon, 11.01.16 18:30, Muayyad AlSadi (alsadi@xxxxxxxxx) wrote:
> quoted from systemd.serivce manual page
>
> >> it is recommended to also use the PIDFile= option, so that systemd can
> identify the main process of the daemon.
>
> my point is that having a child double forked does not mean Zookeeper TCP
> port is ready which is as bad as simple which is also does not indicate
> when it's ready
Well, then Zookeeper is simply broken.
Classic UNIX daemons double fork, and only exit in the parent after
the main daemon process (i.e. the "parent"'s grandchild) informed it
that start-up is now complete, and that most importantly pretty much
means two things:
A) The communication channels are established
B) The PID file is now written
That the parent process hangs around until the main daemon did these
two jobs is essential on SysV, so that shell processing can work, as
the parent returning is the trigger for invoking the next shell
script line, which then is supposed to rely on the daemon being up.
systemd makes the same assumptions on SysV here, even though no shell
scriping is involved. If Zookeper doesn't get this right it's borked
on SysV the same way as on systemd, and really should get fixed.
See daemon(7) on some docs how a classic UNIX daemon is supposed to
start up.
Lennart
--
Lennart Poettering, Red Hat
--
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
http://lists.fedoraproject.org/admin/lists/devel@xxxxxxxxxxxxxxxxxxxxxxx
