Will I do agree it's a hack. But it's better than forking in bash. And usually I don't care about the exact time socket/port is active because zookeeper is supposed to handle fail over. On Jan 12, 2016 7:54 PM, "Reindl Harald" <h.rei...@thelounge.net> wrote:
> > > Am 12.01.2016 um 17:41 schrieb Lennart Poettering: > >> On Tue, 12.01.16 17:16, Muayyad AlSadi (als...@gmail.com) wrote: >> >> well. But if you can double fork() in Java you should be fine and can >>>> >>> >>> it seems that zookeeper is doing the fork in the bash script using nohub >>> not in java >>> >>> when it finished setting up its listening socket. You cannot script >>>> >>> >>> typically I loop using "lsof" or "nc" >>> >> >> Such sleep loops are ugly and a hack. It would be much better to fix >> this properly with a clean notification. >> >> Doing such sleep loops will just help keeping up java's bad rep for >> being slow... >> >> Also, what happens if the daemon is configured to listen on some >> different port? Or on multiple ports? Are you parsing the daemon's >> config file too to figure out what to watch for? YUCK! >> > > the Fedora myqld unit does, mine is simplified > > the systemd-behavior that manual "systemctl stop whatever.service" don't > prevent socket activation and fireup again the service is a systemd problem > *you* have to solve if you want widely adopted usage of socket activation > > > -- > devel mailing list > devel@lists.fedoraproject.org > http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org >
-- devel mailing list devel@lists.fedoraproject.org http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org
