On Fri, Feb 20, 2009 at 05:56, <daniel.poc...@barclayscapital.com> wrote: > There was previously some discussion about a greaper binary for > re-starting gmond after a config change.
Well, the usual way to do this is to catch a HUP signal, and do whatever processing is needed. I know that some programs will simply call the "read_config_file()" routine, instead of fullying exec()ing again. > Is it potentially safe for gmond to just execve another gmond? The new > process will use the same PID, same effective UID, same file > descriptors. > Yeah, its probably safe. As I mentioned, I've seen other long running daemons do this. It's worth a try, in any event. > If gmond is already running with reduced privileges (post-setuid), does > it need to gain root privileges again to restart in this way? No. No extra privileges are needed. -- Jesse Becker GPG Fingerprint -- BD00 7AA4 4483 AFCC 82D0 2720 0083 0931 9A2B 06A2 ------------------------------------------------------------------------------ Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H _______________________________________________ Ganglia-developers mailing list Ganglia-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ganglia-developers