I think that the start priority in the gmond.init script should be increased. I recently noticed a minor problem when we had to reboot one of our nodes that had been up since before daylight savings time ended. When the computer booted, its system clock was set an hour in the future and only corrected itself after ntpd was started, which has a start priority of 26 in the RedHat init scripts. Since gmond has a start priority of 20, it broadcast some of its initial metrics with an incorrect timestamp for things like gmond_started and boottime. I assume it would have eventually corrected its data once the metrics were broadcast again, but it would be nice to have it be correct from the beginning. The gmetad.init script should probably also be changed if the gmond.init script is changed. I don't know what a good priority would be, but it should definitely be started after ntpd synchronizes the clock.
~Jason -- /------------------------------------------------------------------\ | Jason A. Smith Email: [EMAIL PROTECTED] | | Atlas Computing Facility, Bldg. 510M Phone: (631)344-4226 | | Brookhaven National Lab, P.O. Box 5000 Fax: (631)344-7616 | | Upton, NY 11973-5000 | \------------------------------------------------------------------/
