On Fri, Apr 24, 2009 at 12:51:38PM -0400, Brian Utterback wrote: > Nicolas Williams wrote: > > - Where is sunman-stability used? > > It isn't. Other SFW projects use it to add attributes on the end of > the man pages, but I am supplying new man pages with the attributes > section already included. I will remove it.
When I looked at the manpages I didn't see the interface stability attributes... > > - Is there a way to force quick timesync (a la ntpdate)? Or must one > > really way up to 1800 seconds in order to be assured that time is > > synchronized (when config/wait_for_sync == true)? > > NTP v4 has a new feature such that adding the keyword "iburst" to a > server line will cause that server to become usable in about 10 > seconds. Without iburst, it takes between 5 and 6 minutes. Oh, that helps a lot (see below). > > - Be careful how you detect restarts. Your current start method does > > not detect this "svcadm stop -s ntp; svcadm start ntp". You may want > > to use a file in /var/run to track whether the clock has been set > > once. > > I have spent a good deal of time thinking about this. I wasn't sure if > it was worth it because I kept coming up with corner cases. The > current implementation always does the ntpdate, so this implementation > is more flexible than the current system. > > How about having a property to determine whether or not to allow a > single large offset other than at boot? But how does the admin make a > one time exception? I'd hate to have to have the admin change the > property, start the service and then change it back. Deleting the file > in /var/run would work too, but that is getting a little too deep into > implementation details than I'd like. The sysadmin can always stop the service and manually run ntpdate or ntpd equivalent. So I'd go with the /var/run file. Nico --
