On Fri, May 09, 2008 at 05:35:25AM +1000, Ken McDonell wrote:
> I'm afraid not.
>
> That was outside the original scope.
>
> And in fact pmie has accumulated so much state about metric meta data
> and historical metric values, that any re-reading of the config file
> would almost certainly mean forgetting all of that and starting again.
>
> Functionally this would be like killing pmie and starting again ...
> which is already supported .. 8^)>
What I really need is a chroot-safe way to reload pmie.
You can't do `/etc/init.d/pmie restart` because that would start pmie
in the chroot.
It seems that many initscripts support a "reload", which checks a PID
file and sends a -HUP signal if they are (in this case) pmie processes.
I need this because I have an RPM with its own pmie rules file. (The
RPM adds a new process to the pmie control file). When this RPM is
upgraded it needs to restart pmie in order to get these new rules
loaded. The catch is that this RPM is frequently installed in a chroot.
mh
--
Martin Hicks || mort@xxxxxxxx || PGP/GnuPG: 0x4C7F2BEE
|