Re: clock on alic3 board

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
From: riwanlky
Date: Tuesday, July 22, 2008 - 2:35 am

Hai,

Sorry to bother you again, however doing
ntpd -s

I got

# tail -f /var/log/daemon
Jul 21 15:04:29 pceng4 ntpd[8943]: listening on 192.168.1.200
Jul 21 15:04:29 pceng4 ntpd[8943]: listening on fe80:1::20d:b9ff:fe14:ef48
Jul 21 15:04:29 pceng4 ntpd[8943]: listening on 192.168.10.200
Jul 21 15:04:29 pceng4 ntpd[8943]: listening on fe80:2::20d:b9ff:fe14:ef49
Jul 21 15:04:29 pceng4 ntpd[8943]: listening on 192.168.3.200
Jul 21 15:04:29 pceng4 ntpd[8943]: listening on fe80:4::20b:6bff:fe87:6739
Jul 21 15:04:29 pceng4 ntpd[8943]: ntp engine ready
Jul 22 15:13:13 pceng4 ntpd[4869]: set local clock to Tue Jul 22 
15:13:13 WIT 2008 (offset 86923.596141s)
Jul 22 15:13:13 pceng4 ntpd[8943]: 0 out of 1 peers valid
Jul 22 15:13:13 pceng4 ntpd[8943]: bad peer 10.10.10.33 (10.10.10.33)

# ps auxw |grep ntp
_ntp      8943  0.0  0.3   368   796 ??  Is    Mon03PM    0:00.02 ntpd: 
ntp engine (ntpd)
root     31795  0.0  0.2   368   508 ??  Is     3:13PM    0:00.00 ntpd: 
[priv] (ntpd)
root      9797  0.0  0.3   244   732 p0  S+     3:13PM    0:00.01 grep ntp

my ntpd.conf
# cat /etc/ntpd.conf
# $OpenBSD: ntpd.conf,v 1.8 2007/07/13 09:05:52 henning Exp $
# sample ntpd configuration file, see ntpd.conf(5)

# Addresses to listen on (ntpd does not listen by default)
listen on *

# sync to a single server
server 10.10.10.33
#sensor nmea0

Thanks and best regards,
Riwan

Marc Balmer wrote:
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
clock on alic3 board, riwanlky, (Fri Jul 18, 4:57 am)
Re: clock on alic3 board, Marc Balmer, (Fri Jul 18, 6:50 am)
Re: clock on alic3 board, Alexander Hall, (Sat Jul 19, 3:32 am)
Re: clock on alic3 board, Alexander Hall, (Sat Jul 19, 3:50 am)
Re: clock on alic3 board, Marc Balmer, (Sat Jul 19, 4:15 am)
Re: clock on alic3 board, riwanlky, (Tue Jul 22, 2:35 am)