Bugzilla – Bug 732767
PCP init system issues
Last modified: 2014-04-08 14:49:11 UTC
As reported by Ken McDonell, likely fallout from the migration to systemd for openSUSE 12.1: 2. The init.d framework has changed (again!), and now attempts to run /etc/init.d/pcp produce "redirecting to systemctl" as the only message on stdout or stderr and no further indication if this worked, did nothing or failed (without dredging in the tail of /var/log/messages) 3. /etc/init.d/pcp start has become a no-op if the pcp "service" is already running ... you need either an explicit stop and start, or a restart to really restart pmcd Together 2. and 3. break a significant fraction of ALL of the PCP QA. But, wait there is more ... QA 067 KILLS the system ... the last output is "redirecting to systemctl" then clunk, no kernel oops but absolutely nothing works until you power cycle the VM.
It appears that Ken worked around this bug upstream with: commit 1f37d4b8f7dc056d18512639555a38d1c85d43e3 Author: Ken McDonell <kenj@internode.on.net> Date: Fri Dec 2 07:20:21 2011 +1100 common.rc sudo and SUSE changes 1. if sudo supports -E, then always use this ... without preserving the environment when using sudo, the next change does not work! 2. always set the $PCPQA_NO_RC_STATUS environment variable, so we do not use /etc/rc.status in our rc scripts, thereby avoiding systemctl in openSUSE 12.1 and leaving stdout and stderr alone so we can process them in the QA scripts. Note: this needs the matching hack in our rc-proc.sh script to be in place