It appears that the init script for gmond in sys-cluster/ganglia results in gmond starting without creating a pidfile. The attached small patch fixes the problem. Thanks, Josh Reproducible: Always
Created attachment 243411 [details, diff] patch for gmond init script
Created attachment 243413 [details, diff] use pidfile when stopping gmond
Any reason we shouldn't use the built-in --pid-file for both gmond and gmetad? Thanks for reporting.
(In reply to comment #3) > Any reason we shouldn't use the built-in --pid-file for both gmond and gmetad? > > Thanks for reporting. > The only way I can get a PID file that reflects the actual PID of the running gmond process, using start-stop-daemon --pidfile creation is with the following start() function: start() { ebegin "Starting GANGLIA gmond: " start-stop-daemon --start --quiet --background \ --pidfile /var/run/gmond.pid --make-pidfile \ --exec /usr/sbin/gmond -- --foreground eend $? "Failed to start gmond" } That is more complicated than the attached patch, though I could be doing something wrong? Regards, Josh
My apologies for confusing you, I looked at your first patch too quickly, then suggested that you do exactly what it already did. Thanks for reporting, 25 Aug 2010; Justin Bronder <jsbronder@gentoo.org> +files/gmetad.rc-2, +files/gmond.rc-2, -ganglia-3.1.7-r1.ebuild, +ganglia-3.1.7-r2.ebuild: Use pidfile for starting and stopping the ganglia daemons. Thanks to Joshua Rich, #333275
(In reply to comment #5) > My apologies for confusing you, I looked at your first patch too quickly, then > suggested that you do exactly what it already did. > > Thanks for reporting, > > > 25 Aug 2010; Justin Bronder <jsbronder@gentoo.org> +files/gmetad.rc-2, > +files/gmond.rc-2, -ganglia-3.1.7-r1.ebuild, +ganglia-3.1.7-r2.ebuild: > Use pidfile for starting and stopping the ganglia daemons. Thanks to > Joshua Rich, #333275 > Thanks Justin. Regards, Josh
