/me starts singing the NTP song: sync your clock... sync your clock... do it so that the heartbeats don't get dropped :) Your clock is off by 3424 seconds :) Btw, you could have mailed info@sixxs.net for a prompter response :)

That's true... i have not seen the clock problem.. i have rebooted after the big blackdown in italy. Now the clock is good, and ntp is working.. but ipv6 seems not :( Other suggestion? Sandro

Short HOWTO for these wanting a "good clock": a) Set timezone to a non-POSIX one. If you had the following before # ln -s /usr/share/zoneinfo/UTC /etc/localtime Use the following now # ln -s /usr/share/zoneinfo/right/UTC /etc/localtime This applies only if your OS has the right/ subdirectory. Some OSes have the "right/" ones in "./" as well, and the broken ones are _only_ in "posix/". A comparision: -r--r--r-- 6 root bin 56 Oct 20 18:45 /usr/share/zoneinfo/posix/UTC -r--r--r-- 6 root bin 232 Oct 20 18:46 /usr/share/zoneinfo/right/UTC (this is on OpenBSD; MirBSD doesn't include posix any more) If your timezone is something like Europe/Berlin, use right/Europe/Berlin (make sure the file exists) etc. b) Download the source: $ env CVS_RSH=ssh cvs -qz3 -d mirbsd-cvs@mirbsd.bsdadvocacy.org:/cvs \ > co -PA src/usr.sbin/rdate c) Compile the source: c.1] BSD # cd src/usr.sbin/rdate; make && make install BINDIR=/usr/sbin c.2] GNU/Linux $ cd src/usr.sbin/rdate $ gcc -static -o rdate -O2 -DNO_UTIL *.c $ strip --strip-all -R .comment -R .note rdate # cp rdate /usr/sbin && chown root:bin /usr/sbin/rdate # chmod 555 /usr/sbin/rdate d) Synchronize # rdate -ncv ptbtime1.ptb.de # rdate -ncav ptbtime2.ptb.de The latter form uses the adjtime() call, which does not make the clock "jump" but slows down or speeds up the clock interrupt by a very small amount until the clocks are synched (takes some 20 or 30 minutes). It's suitable for inclusion in root's crontab. The former sets the time directly, as date(1) would do. This is good for "large" adjustments, but on BSD systems in securelevel 1 or higher, you cannot set the clock backwards. Some GNU/Linux systems just dump core when using the -a parametre. I don't know why (though I used a binary compiled under a different distro, so that may be the case). Time servers are, among the two above: ntp0.nl.net, time.nist.gov(iirc) Google helps you out -- Sample crontab line: tg@odem:/home/tg $ sudo crontab -l | fgrep rdate Password: 53 */3 * * * /usr/bin/nice -20 /usr/sbin/rdate -ncav ptbtime2.ptb.de 2>&1 | /usr/bin/logger -t 'SNTP' In case you don't have CVS, drop me an email and I will send you a tarball of these files. Or, download them one by one from cvsweb: https://MirBSD.BSDadvocacy.org:8890/active/cvsweb.cgi/src/usr.sbin/rdate/ Hint: nearly the same code, but without the "compiles on GNU/Linux just fine with -DNO_UTIL" fixes, has been committed to OpenBSD as well (the leap second bug correction code contributed by yours truly), but the ntpdate maintainer refuses to accept the fix.