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

[Reindl Harald]

Am 11.01.2016 um 14:32 schrieb Muayyad AlSadi:

"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

____________________________________

[root@mail-gw:~]$ systemd-analyze blame | grep clamd
         10.750s clamd.service
____________________________________

[root@mail-gw:~]$ systemctl status clamd
  clamd.service - ClamAV Scanner Daemon

 Main PID: 5402 (clamd)
   CGroup: /system.slice/clamd.service
           ??5402 /usr/sbin/clamd -c /etc/clamd.d/scan.conf
____________________________________

[root@mail-gw:~]$ cat /etc/systemd/system/clamd.service
[Unit]
Description=ClamAV Scanner Daemon

[Service]
Type=forking
Environment="TMPDIR=/tmp"
Environment="LANG=en_GB.UTF-8"
ExecStart=/usr/sbin/clamd -c /etc/clamd.d/scan.conf
ExecReload=/usr/bin/kill -HUP $MAINPID
Restart=always
RestartSec=1
Nice=5

User=clamscan
Group=clamilt

PrivateTmp=yes
PrivateDevices=yes
NoNewPrivileges=yes
CapabilityBoundingSet=CAP_KILL

SystemCallArchitectures=x86-64

ReadOnlyDirectories=/etc
ReadOnlyDirectories=/usr
ReadOnlyDirectories=/var/lib

*nothing* needs a PID file path because systemd knows the main-PID since it's a supervisor - in fact for most services throwing warnings because the pid-file the solotuin from F15 until now was clone the systemd-unit below /etc/systemd/system/ and remove the line Loaded: loaded (/etc/systemd/system/clamd.service; enabled; vendor preset: disabled) Active: active (running) since Di 2015-12-22 12:40:33 CET; 2 weeks 6 days ago RestrictAddressFamilies=~AF_APPLETALK AF_ATMPVC AF_AX25 AF_IPX AF_NETLINK AF_PACKET AF_X25

signature.asc
Description: OpenPGP digital signature

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