Does "systemctl daemon-reload" discard service information?

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

 



Hi!

I have had the effect that a "systectl status" before and after a
"daemon-reload" is different, while the service in question wasn't restarted:

h02:~ # systemctl status iotwatch@*
● iotwatch@VAR.service - iotwatch I/O performance monitor instance "VAR"
   Loaded: loaded (/etc/iotwatch.conf; disabled; vendor preset: disabled)
   Active: active (running) since Mon 2019-05-20 15:17:25 CEST; 5min ago
     Docs: man:iotwatch(1)
           man:iotwatch@.service(8)
  Process: 15115 ExecStop=/var/run/iotwatch-VAR/iotwatch-VAR -l
/var/log/iotwatch/VAR/iotwatch-VAR.log -m I
-p/var/run/iotwatch-VAR/iotwatch-VAR.pid -d0
-OS:T=F75,S:M=O52,N:3.29/60,Q:C=120,P:nagios.nagios=0664 (code=exited,
status=0/SUCCESS)
  Process: 15149 ExecStartPost=/usr/bin/sleep 0.2 (code=exited,
status=0/SUCCESS)
  Process: 15146 ExecStart=iotwatch-VAR -l
/var/log/iotwatch/VAR/iotwatch-VAR.log -m I
-p/var/run/iotwatch-VAR/iotwatch-VAR.pid -d1 -a0.00 -b512 -i4 -sD -t0.5
-TX=0.25:0.50,A=0.025:0.05 -OR
-OS:T=F75,S:M=O52,N:3.29/60,Q:C=120,P:nagios.nagios=0664 /dev/sys/var
(code=exited, status=0/SUCCESS)
  Process: 15143 ExecStartPre=/bin/sh -c [ -d "/var/log/iotwatch/VAR" -o 1 -eq
0 ] || mkdir "/var/log/iotwatch/VAR" || exit 3 (code=exited, status=0/SUCCESS)
  Process: 15139 ExecStartPre=/bin/sh -c [ -h
"/var/run/iotwatch-VAR/iotwatch-VAR" ] || ln -s "/usr/bin/iotwatch"
"/var/run/iotwatch-VAR/iotwatch-VAR" || exit 3 (code=exited, status=0/SUCCESS)
  Process: 15136 ExecStartPre=/bin/sh -c [ -d "/var/run/iotwatch-VAR" ] ||
mkdir "/var/run/iotwatch-VAR" || exit 3 (code=exited, status=0/SUCCESS)
 Main PID: 15148 (iotwatch-VAR)
    Tasks: 4 (limit: 512)
   CGroup: /system.slice/system-iotwatch.slice/iotwatch@VAR.service 
           └─15148 iotwatch-VAR -l /var/log/iotwatch/VAR/iotwatch-VAR.log -m I
-p/var/run/iotwatch-VAR/iotwatch-VAR.pid...

May 20 15:17:24 h02 systemd[1]: Starting iotwatch I/O performance monitor
instance "VAR"...
May 20 15:17:25 h02 systemd[1]: Started iotwatch I/O performance monitor
instance "VAR".
Warning: iotwatch@VAR.service changed on disk. Run 'systemctl daemon-reload'
to reload units.
h02:~ # systemctl daemon-reload
h02:~ # systemctl status iotwatch@*
● iotwatch@VAR.service - iotwatch I/O performance monitor instance "VAR"
   Loaded: loaded (/etc/iotwatch.conf; disabled; vendor preset: disabled)
   Active: active (running) since Mon 2019-05-20 15:17:25 CEST; 5min ago
     Docs: man:iotwatch(1)
           man:iotwatch@.service(8)
 Main PID: 15148 (iotwatch-VAR)
    Tasks: 4 (limit: 512)
   CGroup: /system.slice/system-iotwatch.slice/iotwatch@VAR.service 
           └─15148 iotwatch-VAR -l /var/log/iotwatch/VAR/iotwatch-VAR.log -m I
-p/var/run/iotwatch-VAR/iotwatch-VAR.pid...

May 20 15:17:24 h02 systemd[1]: Starting iotwatch I/O performance monitor
instance "VAR"...
May 20 15:17:25 h02 systemd[1]: Started iotwatch I/O performance monitor
instance "VAR".

Is that intentional?

Regards,
Ulrich

_______________________________________________
systemd-devel mailing list
systemd-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/systemd-devel




[Index of Archives]     [LARTC]     [Bugtraq]     [Yosemite Forum]     [Photo]

  Powered by Linux