Here is what I propose in the V4 code: In V4, ntpdate is no longer used. Instead, the NTP has a new mode that is used only on the first synchronization. It goes into a super fast mode that gets an offset to within a second in about 5 seconds instead of the 5 minutes previously needed. It will then correct this offset, regardless of the magnitude, just as ntpdate does now. It will do this just once, afterward imposing a 20 minute maximum offset.
All of that happens in the background of course. In addition, there will be a program that will monitor the state NTP program and wait until certain conditions are met, thus preventing the method from exiting. We will have a SMF property that will tell the monitor program to exit no matter what, to exit after the first clock setting or to wait for the first clock setting with a maximum wait time. I would also like to be able to get an NTP server through DHCP, but I need to talk to the NWAM and DHCP people about that. Michael Schuster wrote: > Brian Utterback wrote: >> What should the behavior of SMF be in regard to NTP? If you have >> it configured then I think you expect it to work. If it does not, >> then something needs to be done to fix it. For some users NTP >> is an absolute requirement. For others it is optional. And for >> others, they just don't care. > > I completely agree. In my case, I'd like to have ntp work if it finds a > server (I have multicast client configured), but if it doesn't, it > shouldn't keep me from getting on with my stuff. > I know I can re-arrange dependencies, but that's a rather heavy-handed > approach, and thought maybe someone has a better idea. > > Michael -- blu Screening ideas are indeed thought up by the Office for Annoying Air Travelers and vetted through the Directorate for Confusion and Complexity - Kip Hawley, Head of the TSA ---------------------------------------------------------------------- Brian Utterback - Solaris RPE, Sun Microsystems, Inc. Ph:877-259-7345, Em:brian.utterback-at-ess-you-enn-dot-kom _______________________________________________ networking-discuss mailing list [email protected]
