| 1 |
Peter Humphrey wrote: |
| 2 |
> On Friday 07 January 2011 22:48:27 Dale wrote: |
| 3 |
> |
| 4 |
> |
| 5 |
>> Any other ideas? |
| 6 |
>> |
| 7 |
> You could still try chrony. |
| 8 |
> |
| 9 |
> |
| 10 |
|
| 11 |
Success !!!!!! Check this out: |
| 12 |
|
| 13 |
root@fireball / # ntpdate -b -u -q pool.ntp.org |
| 14 |
server 169.229.70.183, stratum 3, offset 0.009525, delay 0.12221 |
| 15 |
server 216.45.57.38, stratum 2, offset 0.000842, delay 0.12035 |
| 16 |
server 63.211.239.58, stratum 2, offset 0.009992, delay 0.09676 |
| 17 |
8 Jan 15:39:49 ntpdate[7402]: step time server 63.211.239.58 offset |
| 18 |
0.009992 sec |
| 19 |
root@fireball / # |
| 20 |
|
| 21 |
Now, with ntp, it logs to messages when it syncs, resets the clock and |
| 22 |
such. Does chrony do this somewhere too? I have this in my conf file: |
| 23 |
|
| 24 |
server 64.6.144.6 |
| 25 |
server 67.159.5.90 |
| 26 |
server 67.59.168.233 |
| 27 |
server 204.62.14.98 |
| 28 |
server 69.50.219.51 |
| 29 |
server 209.114.111.1 |
| 30 |
driftfile /etc/chrony.drift |
| 31 |
logdir /var/log/chrony |
| 32 |
|
| 33 |
I would think it would be either in messages or in /var/log/chrony but |
| 34 |
so far nothing is in there. This is from messages: |
| 35 |
|
| 36 |
root@fireball / # cat /var/log/messages | grep chron | tail -n 50 |
| 37 |
Jan 8 03:16:52 localhost chronyd[21986]: chronyd exiting on signal |
| 38 |
Jan 8 03:16:53 localhost chronyd[23021]: chronyd version 1.24 starting |
| 39 |
Jan 8 03:16:53 localhost chronyd[23021]: Initial txc.tick=10006 |
| 40 |
txc.freq=94656 (1.44433594) txc.offset=0 => hz=100 shift_hz=7 |
| 41 |
Jan 8 03:16:53 localhost chronyd[23021]: set_config_hz=0 hz=100 |
| 42 |
shift_hz=7 basic_freq_scale=1.28000000 nominal_tick=10000 |
| 43 |
slew_delta_tick=833 max_tick_bias=1000 |
| 44 |
Jan 8 03:16:53 localhost chronyd[23021]: Linux kernel major=2 minor=6 |
| 45 |
patch=36 |
| 46 |
Jan 8 03:16:53 localhost chronyd[23021]: |
| 47 |
calculated_freq_scale=1.00000000 freq_scale=1.00000000 |
| 48 |
Jan 8 03:19:03 localhost chronyd[23021]: Selected source 64.6.144.6 |
| 49 |
Jan 8 15:24:56 localhost chronyd[23021]: chronyd exiting on signal |
| 50 |
Jan 8 15:24:56 localhost chronyd[1632]: chronyd version 1.24 starting |
| 51 |
Jan 8 15:24:56 localhost chronyd[1632]: Initial txc.tick=10011 |
| 52 |
txc.freq=2399519 (36.61375427) txc.offset=0 => hz=100 shift_hz=7 |
| 53 |
Jan 8 15:24:56 localhost chronyd[1632]: set_config_hz=0 hz=100 |
| 54 |
shift_hz=7 basic_freq_scale=1.28000000 nominal_tick=10000 |
| 55 |
slew_delta_tick=833 max_tick_bias=1000 |
| 56 |
Jan 8 15:24:56 localhost chronyd[1632]: Linux kernel major=2 minor=6 |
| 57 |
patch=36 |
| 58 |
Jan 8 15:24:56 localhost chronyd[1632]: |
| 59 |
calculated_freq_scale=1.00000000 freq_scale=1.00000000 |
| 60 |
Jan 8 15:27:07 localhost chronyd[1632]: Selected source 64.6.144.6 |
| 61 |
root@fireball / # |
| 62 |
|
| 63 |
Ideas? I miss something somewhere? Do I have to create a file for it |
| 64 |
to log to as well? |
| 65 |
|
| 66 |
Dale |
| 67 |
|
| 68 |
:-) :-) |
| 69 |
|
| 70 |
P. S. I wonder why ntp and openntp didn't work? |
Archives