...
Oct 26 13:37:30 center PAM_pwdb[6874]: 1 authentication failure;
(uid=0) -> ...
rtc_time : 12:02:06 ---timestamp---
Oct 26 13:41:03 center diald[409]: SIGUSR1. External link up request
received.
...
Oct 26 14:10:00 center diald[409]: SIGUSR1. External link up request
received.
rtc_time : 13:64:01 ---timestamp---
Oct 26 14:10:01 center diald[409]: Running connect (pid =
7308).
...
I have this entry in /etc/crontab:
10,25,40,55 * * * * root echo `grep -e rtc_time /proc/rtc`
---timestamp--->>/var/log/messages
10 9-23 * * 1-5 root killall -USR1 diald
And such ip-up_script for diald:
/usr/sbin/sendmail -q
/usr/bin/fetchmail -s
/usr/sbin/ntpdate -s -t 10 ntp.css.gov ntp5.tamu.edu
/sbin/hwclock --systohc
This script updates time every hour in my system pretty correctly, but
it seems to be
that later clocks become unsinchronized until next diald's bring up.
But looking
on kernel messages one can think that this is only rtc problem.
I'm using 2.0.36-pre13.
Btw on 2.0.35 all was ok.
Vinche.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/