On 17 September 2012 21:47, Bob Proulx <b...@proulx.com> wrote: > Mauro wrote: >> I think ntpd crashes are because my server lost time. >> I have ntpd in two server, now I've seen that in one of these ntp >> crashes and the time of the server is 1 hour forward. >> That's why ntp crashes: server time goes 1 hour forward and ntp can't >> resynchronize so it crashes. > > Is it really crashing or is this intended behavior. The ntpd is > documented with: > > -g Normally, ntpd exits with a message to the system log if the > offset exceeds the panic threshold, which is 1000 s by > default. This option allows the time to be set to any value > without restriction; however, this can happen only once. If > the threshold is exceeded after that, ntpd will exit with a > message to the system log. This option can be used with the > -q and -x options. > > Therefore if the time is one hour forward that will be greater than > the threshold 1000 seconds and ntp will exit. As described this is so > that the admin may adjust the time manually to some specific value > (for whatever reason, testing, whatever) and ntpd will get out of the > way. > > It also says that ntpd will log a message to the system log when this > condition occurs.
No message logs. > > I think it is possible that you have some additional process that is > setting the clock and this is jumping the time forward one hour and > because the time is jumped forward one hour that exceeds the ntpd > panic threshold and therefore ntpd decides that it should get out of > the way and it intentionally exits. This intentional behavior is > quite a bit different from a crash. I have no additional processes. Now I'm trying openntp. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAE17a0WNw_a=vtptnu3mh4_kd_zx6kays8qorsumyivqfyt...@mail.gmail.com
