pcp
[Top] [All Lists]

Re: [pcp] debian bug #544350 (daemons starting by default)

To: Martin Hicks <mort@xxxxxxx>
Subject: Re: [pcp] debian bug #544350 (daemons starting by default)
From: Mark Goodwin <goodwinos@xxxxxxxxx>
Date: Wed, 14 Oct 2009 09:47:27 +1100
Cc: pcp@xxxxxxxxxxx
In-reply-to: <20091013123814.GN11060@xxxxxxxxxxxxxxxxxxxxxxxxx>
References: <20091013123814.GN11060@xxxxxxxxxxxxxxxxxxxxxxxxx>
User-agent: Thunderbird 2.0.0.21 (X11/20090320)
Martin Hicks wrote:
This is a follow-up to a long IRC conversation last night between Mark
and Nathan on IRC.

To start with, I'm going to put the default run levels back how they were.
Then fix the Red Hat default run-levels and give it a thorough test,
including upgrades, etc. This needs to be done fairly quickly to resolve
the deb bug, and also to get PCP into Fedora. I'd propose this is all
we take for 3.0.1 unless anyone else has anything similarly urgent?


If we need to have runnable init.d scripts for all services, I'm quite
sure that I've seen debian disable services by having a variable set in
/etc/default/<service> something like:

ENABLED=

and the init.d script checking that before starting the daemon.

Well I'll leave that investigation and enhancement to Nathan since
it looks like it's mostly a deb thing (?)


Would this approach suffice for having init.d scripts for pmie and
pmproxy, without running the daemons?


the current situation on deb certainly seems like an anomaly to me -
a freshly installed service that needs admin config before it can
function, can't possibly be expected to be enabled by default ..?

Cheers
-- Mark

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