1 |
Good morning all, |
2 |
|
3 |
About 10 days ago we had a lightning strike very nearby that fried our |
4 |
electric utilities transformer and my APC RS800 UPS. This in turn caused |
5 |
my system to crash. When I brought it back up, all CMOS settings had been |
6 |
lost. After setting what I could remember (no, I didn't have them written |
7 |
down), I brought Gentoo back up. Massive complaints about the time being |
8 |
off (I had forgotten to set the hardware clock). |
9 |
|
10 |
# /etc/init.d/ntpd stop |
11 |
followed by |
12 |
# ntpdate pool.ntp.org |
13 |
set the system time correctly. So I |
14 |
#/etc/init.d/ntpd start |
15 |
|
16 |
Since then, ntpd does not work. |
17 |
According to ps, ntpd is running |
18 |
|
19 |
//garbanzo/etc # ps aux|grep ntp |
20 |
root 19874 0.0 0.3 3656 3656 ? SLs 09:05 0:00 |
21 |
/usr/sbin/ntpd -p /var/run/ntpd.pid |
22 |
|
23 |
But all that shows in the /var/log/ntp.log is |
24 |
12 Jun 09:05:46 ntpd[19515]: ntpd exiting on signal 15 |
25 |
|
26 |
I've also noticed that the software clock is running about 2 minutes fast |
27 |
per hour. I know I could setup a cron job to run ntpdate regularly, but |
28 |
that is the wrong solution. ntpd had been working fine for years. |
29 |
|
30 |
Does anyone have any possible ideas what could have happened here? |
31 |
|
32 |
Thanks, |
33 |
festus |
34 |
|
35 |
-- |
36 |
It is not unusual for those at the wrong end of the club to have a |
37 |
clearer picture of reality than those who wield it. |
38 |
Noam Chomsky |
39 |
-- |
40 |
gentoo-user@g.o mailing list |