> "Type=forking" implies that depending services are started *after* the forking and the service is *really* read (it needs depending on the signatures a longer time for initalization)
but I guess it needs a PID file path to work properly which is not the case.
I'm not really sure about the readyness thingy in case of zookeeper but I guess both simple and forking do not know when exactly the when port is opened (I guess only notify does that)
On Mon, Jan 11, 2016 at 3:18 PM, Reindl Harald <h.reindl@xxxxxxxxxxxxx> wrote:
type simple don't come without drawbacks
Am 11.01.2016 um 14:06 schrieb Muayyad AlSadi:
hi,
in fedora's zookeeper service < /usr/lib/systemd/system/zookeeper.service
we have the following line
ExecStart=/usr/bin/zkServer.sh start zoo.cfg
why not
ExecStart=/usr/bin/zkServer.sh start-foreground zoo.cfg
of type simple
specially that file does not contain "PIDFile=" directive
depending service shave *no idea* if it is ready
the "clamd" service as example comes with "Type = simple" which means when you are using clamav-milter you get at boot a ton of warnings while "Type=forking" implies that depending services are started *after* the forking and the service is *really* read (it needs depending on the signatures a longer time for initalization)
--
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
http://lists.fedoraproject.org/admin/lists/devel@xxxxxxxxxxxxxxxxxxxxxxx
-- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx http://lists.fedoraproject.org/admin/lists/devel@xxxxxxxxxxxxxxxxxxxxxxx
