Okay, so I guess in the 'new' code we will check to see if it already has a valid working ntp server entry, if not, then use the default (pool.ntp.org).
Not quite. We define the default as the current value if ntp is working, otherwise pool.ntp.org.
Remember, the "principle of least surprise" is very much a hallmark of good UNIX design.
But the whole point of the ntpconfig package is so that you can change the ntp server to whatever you choose, with the GUI.
And so it shall remain. But, we'll only blow away a correctly working configuration if we're told to do that.
So, assuming a working config, the GUI will present three choices:
Current working value
pool.ntp.org
noneThe "current working value" shall be the default; the last item is per Michael Edwards' request.
If there is a current default, but it doesn't work, and pool.ntp.org does work, we could make the latter the default. If neither works, I would leave the current value as the default -- it's certainly no worse than pool.ntp.org.
We should define "works" as "allows ntp two operate."
-- David N. Lombard Rossmoor, Orange County, CA http://www.fourmilab.ch/cgi-bin/uncgi/Earth?imgsize=320&opt=-z&lat=33.8&ns=North&lon=118.08&ew=West&alt=7&img=learth.evif
------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ Oscar-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oscar-devel
