Hello.
Kurt Roeckx wrote:
ntp does not tell the kernel to do so. The kernel does so when
it the clock is synchronized. That is when the status !=
STA_UNSYNC. But it is true that only ntpd sets this and not
ntpdate. I'm not sure it's a good idea to set this in something
like ntpdate or since it might only runs once. The current
implementation only seems to be doing this after an adjtimex()
call.
I don't understand why it isn't a good idea to do it in ntpdate.
Doesn't ntpdate get an accurate time at the moment it runs that
should be more accurate than the RTC?
Sorry, I am not an expert though I would like to know why that is a
bad idea.
Thanks for your info!
Have a nice day!
--
Ivan Baldo - iba...@adinet.com.uy - http://ibaldo.codigolibre.net/
From Montevideo, Uruguay, at the south of South America.
Freelance programmer and GNU/Linux system administrator, hire me!
Alternatives: iba...@codigolibre.net - http://go.to/ibaldo
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
