pcp
[Top] [All Lists]

Re: [pcp] systemctl issue for QA on openSuSE 12.1

To: Ken McDonell <kenj@xxxxxxxxxxxxxxxx>
Subject: Re: [pcp] systemctl issue for QA on openSuSE 12.1
From: Nathan Scott <nathans@xxxxxxxxxx>
Date: Wed, 3 Sep 2014 19:33:52 -0400 (EDT)
Cc: PCP <pcp@xxxxxxxxxxx>
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <54079C6B.9060901@xxxxxxxxxxxxxxxx>
References: <54079C6B.9060901@xxxxxxxxxxxxxxxx>
Reply-to: Nathan Scott <nathans@xxxxxxxxxx>
Thread-index: VqnM1mBADhGbbPvStyc6cHEleARiVw==
Thread-topic: systemctl issue for QA on openSuSE 12.1
Hi Ken,

----- Original Message -----
> kenj@vm02:~/src/pcp/qa$ sudo systemctl enable pmlogger.service
> pmlogger.service is not a native service, redirecting to /sbin/chkconfig.
> Executing /sbin/chkconfig pmlogger on
> 
> For this platform, either ...
> 
> 1. systemctl is not the right choice (this is what qa/common.check uses), or
> 2. we're not installing our stuff as "native service"(s)
> 
> The end result is that we're getting QA failures from the "redirecting" and
> "Executing" lines.
> 
> I don't know what the right fix is here ... help.

$ pkg-config systemd --variable=systemdsystemunitdir

Will tell you where the unit files are going to end up after
the configure process.  Firstly, I'd peek in there and see if
a/ pmlogger.service is there and looks "sane" (not corrupt or
zero length, or something else wierd) and b/ if it looks like
every other service file in that dir (permissions, contents).

Is the pmcd service starting OK or does it have the same issues?
If its OK, begs the question as to what's different between 'em?

cheers.

--
Nathan

<Prev in Thread] Current Thread [Next in Thread>