http://bugzilla.novell.com/show_bug.cgi?id=727771
http://bugzilla.novell.com/show_bug.cgi?id=727771#c65
--- Comment #65 from LTC BugProxy
Created attachment 100321 [details] testconf
Stripped down version of the dumpconf service:
The "start" function of this service script forks itself as a new background process with parameters "start background" and then exits.
The background process does the following:
1) It creates a PID file "/var/run/testconf.pid" 2) Sleeps for 2 seconds 3) Removes the PID file 4) Exits
Installation:
1) Copy "testconf" init script to /etc/init.d/ 2) Issue: chkconfig --add testconf
Execution:
1) Issue: service testconf start 2) Inspect /tmp/testconf.log
In the log on LPAR I see the following:
PPID=1 PID=24510: start PPID=1 PID=24510: The activation of testconf is being delayed PPID=1 PID=24510: start done PPID=1 PID=24510: exit PPID=1 PID=24516: start PPID=1 PID=24516: The background process PPID=1 PID=24516: sleep: 0 PPID=1 PID=24516: sleep: 1 PPID=1 PID=24516: start done PPID=1 PID=24516: exit PPID=1 PID=24525: stop <--- ???? PPID=1 PID=24525: do stop PPID=1 PID=24525: stop done PPID=1 PID=24525: exit
The question to the SUSE systemd experts is:
Why is systemd calling "testconf stop" (PID=24525) after the testconf background process has exited?
Tested on zEC12 LPAR with SLES12.1-Beta2 kernel 3.12.46-2-default #rpm -qi systemd Name : systemd Version : 210 Release : 73.6 Architecture: s390x Install Date: Tue Aug 25 14:24:37 2015 Group : System/Base Size : 12866072 License : LGPL-2.1+ Signature : RSA/SHA256, Wed Aug 19 04:07:47 2015, Key ID 70af9e8139db7c82 Source RPM : systemd-210-73.6.src.rpm Build Date : Wed Aug 19 04:05:37 2015 Build Host : s390lpd Relocations : (not relocatable) Packager : https://www.suse.com/ Vendor : SUSE LLC https://www.suse.com/ URL : http://www.freedesktop.org/wiki/Software/systemd Summary : A System and Session Manager Description : Systemd is a system and service manager, compatible with SysV and LSB init scripts for Linux. systemd provides aggressive parallelization capabilities, uses socket and D-Bus activation for starting services, offers on-demand starting of daemons, keeps track of processes using Linux cgroups, supports snapshotting and restoring of the system state, maintains mount and automount points and implements an elaborate transactional dependency-based service control logic. It can work as a drop-in replacement for sysvinit. Distribution: SUSE Linux Enterprise 12 tried testconf service #cat /tmp/testconf.log PPID=1 PID=32522: start PPID=1 PID=32522: The activation of testconf is being delayed PPID=1 PID=32522: start done PPID=1 PID=32522: exit PPID=1 PID=32528: start PPID=1 PID=32528: The background process PPID=1 PID=32528: sleep: 0 PPID=1 PID=32528: sleep: 1 PPID=1 PID=32528: start done PPID=1 PID=32528: exit no stop observed. also # cat /etc/sysconfig/dumpconf | grep -v "^#" | grep "=" ON_PANIC="dump_reipl" DELAY_MINUTES="1" DUMP_TYPE="ccw" DEVICE="0.0.7e69" WWPN="" LUN="" BOOTPROG="0" BR_LBA="0" VMCMD_1="" VMCMD_2="" VMCMD_3="" VMCMD_4="" VMCMD_5="" VMCMD_6="" VMCMD_7="" VMCMD_8="" # lsshut Trigger Action ======================== Halt stop Power off stop Reboot reipl Restart dump_reipl Panic dump_reipl # systemctl status dumpconf.service dumpconf.service - LSB: Configure s390 dump feature Loaded: loaded (/etc/init.d/dumpconf) Active: active (exited) since Tue 2015-08-25 11:59:33 MSK; 1min 36s ago Process: 32741 ExecStop=/etc/init.d/dumpconf stop (code=exited, status=0/SUCCESS) Process: 32754 ExecStart=/etc/init.d/dumpconf start (code=exited, status=0/SUCCESS) Aug 25 11:59:33 p23lp33 dumpconf[32754]: The activation of dumpconf is being delayed for 1 minutes Aug 25 11:59:33 p23lp33 systemd[1]: Started LSB: Configure s390 dump feature. no stop observed. # rpm -q systemd s390-tools systemd-210-73.6.s390x s390-tools-1.24.1-43.20.s390x -- You are receiving this mail because: You are on the CC list for the bug.