Re: is there a reason for starting zookeeper.service in background?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 





Am 12.01.2016 um 17:41 schrieb Lennart Poettering:
On Tue, 12.01.16 17:16, Muayyad AlSadi (alsadi@xxxxxxxxx) 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

Attachment: signature.asc
Description: OpenPGP digital signature

--
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
http://lists.fedoraproject.org/admin/lists/devel@xxxxxxxxxxxxxxxxxxxxxxx

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux