The daemon in question is xntpd. If xntpd decides that the offset is greater than some threshold, instead of correcting it, it prints an error message and exits. The intent was that a human needs to respond and decide how to fix the problem.
That was fine up until Solaris 10. With Solaris 10 the restarter will see that xntpd has exited and then re-start it. The start up method runs ntpdate, which does not have the threshold and will set the clock. The xntpd deamon then starts up and goes on its merry way. So, to go back to the previous behavior, we want the restarter to not restart xntpd. So, that's why we want to go into maintenance mode. David Bustos wrote: > Quoth Brian Utterback on Fri, Apr 27, 2007 at 01:18:13PM -0400: >> Okay, now I am a bit confused. What I want is for my daemon to exit, >> marking the service as in maintenance mode and for the daemon to not >> be restarted. Rebooting should but everything back to normal. So, >> do I use smf_maintain_instance or smf_disable_instance or both, with >> SMF_IMMEDIATE or SMF_TEMPORARY or both flags. And should I exit, or >> wait for SMF to kill the daemon. Or should I use smf_get_state to >> test the stae before exiting on my own? > > Why do you want your service to appear in the maintenance state? > > > David -- blu "When Congress started Daylight Savings Time earlier, did they even consider what affect an extra hour of daylight would have on global warming? Well, did they?" ---------------------------------------------------------------------- Brian Utterback - Solaris RPE, Sun Microsystems, Inc. Ph:877-259-7345, Em:brian.utterback-at-ess-you-enn-dot-kom
