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 20:02:22 -0400 (EDT)
Cc: PCP <pcp@xxxxxxxxxxx>
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <5407AB2E.9080908@xxxxxxxxxxxxxxxx>
References: <54079C6B.9060901@xxxxxxxxxxxxxxxx> <1677609058.43609677.1409787232939.JavaMail.zimbra@xxxxxxxxxx> <5407AB2E.9080908@xxxxxxxxxxxxxxxx>
Reply-to: Nathan Scott <nathans@xxxxxxxxxx>
Thread-index: IzaH3IwYQn6MqdI0/wBgZ2mhd8mZFw==
Thread-topic: systemctl issue for QA on openSuSE 12.1

----- Original Message -----
> On 04/09/14 09:33, Nathan Scott wrote:
> > ...
> > $ pkg-config systemd --variable=systemdsystemunitdir
> >
> > Will tell you where the unit files are going to end up after
> > the configure process. ...
> 
> Nope.  That command returns no output.
> 

Ah, it should be like...
$ pkg-config systemd --variable=systemdsystemunitdir
/usr/lib/systemd/system

... so, hmmm, yeah, this is probably a big part of the problem.  In
this case I think configure should be switching off systemd support
and falling back to the original rc.d methods.

Can you do a check build with "./Makepkgs --without-systemd" for
this host, and then check QA?  I'll go have a look at the configure
script to see how this became enabled with no unitdir path.

cheers.

--
Nathan

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