Re: [Comm] Branch 4.1 - не работает синхронизация времени?

["Владимир Гусев" <vova1971@narod.ru>]

[-- Attachment #1: Type: text/plain, Size: 494 bytes --]

> > Я не говорю о раздаче - я говорю о времени на отдельно взятом компе
> > - не синхронизируется, несмотря на установки. Почему не стартует
> > ntpd? Зачем он тогда там нужен включенный? Где сервис?
> 
> Что говорит 
> #ntpd -d ?

См. аттач к письму. 



-- 
С уважением,
Владимир Гусев

[-- Attachment #2: ntpd.log --]
[-- Type: text/x-log, Size: 6939 bytes --]

[root@book ~]# ntpd -d
ntp engine ready
reply from 85.21.125.66: offset -26.068185 delay 0.004062, next query 8s
reply from 212.100.132.50: offset -26.108687 delay 0.023096, next query 6s
reply from 193.125.143.173: offset -26.109478 delay 0.025784, next query 9s
reply from 194.33.191.69: offset -26.098280 delay 0.030128, next query 7s
reply from 212.100.132.50: offset -26.108423 delay 0.023198, next query 7s
reply from 194.33.191.69: offset -26.098062 delay 0.030000, next query 9s
reply from 85.21.125.66: offset -26.067662 delay 0.003505, next query 7s
reply from 193.125.143.173: offset -26.109508 delay 0.023702, next query 5s
reply from 212.100.132.50: offset -26.108194 delay 0.023311, next query 6s
reply from 193.125.143.173: offset -26.109451 delay 0.024057, next query 9s
reply from 85.21.125.66: offset -26.067220 delay 0.003309, next query 5s
reply from 194.33.191.69: offset -26.097789 delay 0.030145, next query 8s
peer 212.100.132.50 now valid
reply from 212.100.132.50: offset -26.108048 delay 0.023189, next query 5s
peer 85.21.125.66 now valid
reply from 85.21.125.66: offset -26.067019 delay 0.003179, next query 6s
peer 193.125.143.173 now valid
reply from 193.125.143.173: offset -26.109890 delay 0.025963, next query 5s
reply from 212.100.132.50: offset -26.107906 delay 0.023117, next query 9s
peer 194.33.191.69 now valid
reply from 194.33.191.69: offset -26.097569 delay 0.030036, next query 9s
reply from 85.21.125.66: offset -26.067258 delay 0.004044, next query 5s
reply from 193.125.143.173: offset -26.109031 delay 0.023987, next query 7s
reply from 85.21.125.66: offset -26.066854 delay 0.003881, next query 5s
reply from 212.100.132.50: offset -26.107564 delay 0.023047, next query 5s
reply from 194.33.191.69: offset -26.097266 delay 0.030027, next query 6s
reply from 193.125.143.173: offset -26.108672 delay 0.023919, next query 7s
reply from 85.21.125.66: offset -26.066820 delay 0.003770, next query 33s
reply from 212.100.132.50: offset -26.107435 delay 0.023021, next query 34s
reply from 194.33.191.69: offset -26.096989 delay 0.030178, next query 8s
reply from 193.125.143.173: offset -26.108198 delay 0.024228, next query 33s
reply from 194.33.191.69: offset -26.096768 delay 0.030059, next query 31s
reply from 85.21.125.66: offset -26.065600 delay 0.003894, next query 33s
reply from 212.100.132.50: offset -26.106237 delay 0.023053, next query 33s
reply from 193.125.143.173: offset -26.107095 delay 0.025337, next query 33s
reply from 194.33.191.69: offset -26.095741 delay 0.030114, next query 33s
adjusting local clock by -26.102748s
skiping very first adjtimex
reply from 85.21.125.66: offset -26.052371 delay 0.003128, next query 34s
reply from 212.100.132.50: offset -26.091906 delay 0.023161, next query 34s
reply from 193.125.143.173: offset -26.091608 delay 0.023941, next query 33s
reply from 194.33.191.69: offset -26.078345 delay 0.030150, next query 33s
ntp engine exiting
dispatch_imsg in main: pipe closed
Lost child: child exited
Terminating
[root@book ~]# ntpd -d > /tmp/ntpd.log
ntp engine ready
reply from 85.21.125.66: offset -25.945785 delay 0.003636, next query 8s
reply from 212.100.132.50: offset -25.987514 delay 0.023095, next query 7s
reply from 193.125.143.173: offset -25.988615 delay 0.023870, next query 8s
reply from 194.33.191.69: offset -25.977042 delay 0.030383, next query 9s
reply from 212.100.132.50: offset -25.983827 delay 0.023235, next query 6s
reply from 85.21.125.66: offset -25.941415 delay 0.003288, next query 6s
reply from 193.125.143.173: offset -25.989791 delay 0.034611, next query 6s
reply from 194.33.191.69: offset -25.972456 delay 0.030197, next query 6s
reply from 212.100.132.50: offset -25.980546 delay 0.023126, next query 7s
reply from 85.21.125.66: offset -25.938466 delay 0.004012, next query 5s
reply from 193.125.143.173: offset -25.981191 delay 0.023903, next query 7s
reply from 194.33.191.69: offset -25.969182 delay 0.029918, next query 6s
peer 85.21.125.66 now valid
reply from 85.21.125.66: offset -25.935590 delay 0.003410, next query 5s
peer 212.100.132.50 now valid
reply from 212.100.132.50: offset -25.976755 delay 0.023119, next query 8s
peer 193.125.143.173 now valid
reply from 193.125.143.173: offset -25.977458 delay 0.024048, next query 5s
peer 194.33.191.69 now valid
reply from 194.33.191.69: offset -25.965920 delay 0.029965, next query 7s
reply from 85.21.125.66: offset -25.932980 delay 0.003707, next query 5s
reply from 193.125.143.173: offset -25.974699 delay 0.023745, next query 9s
reply from 212.100.132.50: offset -25.972648 delay 0.023484, next query 5s
reply from 194.33.191.69: offset -25.961423 delay 0.031571, next query 8s
reply from 85.21.125.66: offset -25.930452 delay 0.004016, next query 7s
reply from 212.100.132.50: offset -25.969791 delay 0.023096, next query 5s
reply from 193.125.143.173: offset -25.970010 delay 0.023871, next query 8s
reply from 85.21.125.66: offset -25.926249 delay 0.003291, next query 34s
reply from 194.33.191.69: offset -25.959145 delay 0.033531, next query 5s
reply from 212.100.132.50: offset -25.967673 delay 0.022968, next query 30s
reply from 194.33.191.69: offset -25.955247 delay 0.029961, next query 33s
reply from 193.125.143.173: offset -25.966248 delay 0.023961, next query 31s
reply from 212.100.132.50: offset -25.951621 delay 0.023276, next query 33s
reply from 85.21.125.66: offset -25.908717 delay 0.003828, next query 31s
reply from 193.125.143.173: offset -25.950486 delay 0.025772, next query 30s
reply from 194.33.191.69: offset -25.937573 delay 0.030053, next query 31s
adjusting local clock by -25.968428s
skiping very first adjtimex
reply from 85.21.125.66: offset -25.891957 delay 0.003474, next query 32s
reply from 212.100.132.50: offset -25.934094 delay 0.023087, next query 33s
reply from 193.125.143.173: offset -25.933575 delay 0.023814, next query 30s
reply from 194.33.191.69: offset -25.920995 delay 0.030032, next query 30s
reply from 85.21.125.66: offset -25.874910 delay 0.003645, next query 34s
reply from 212.100.132.50: offset -25.916356 delay 0.022936, next query 31s
reply from 193.125.143.173: offset -25.917767 delay 0.024325, next query 32s
reply from 194.33.191.69: offset -25.904899 delay 0.030253, next query 32s
reply from 212.100.132.50: offset -25.899906 delay 0.023115, next query 34s
reply from 193.125.143.173: offset -25.900560 delay 0.023984, next query 33s
reply from 85.21.125.66: offset -25.856635 delay 0.003674, next query 33s
reply from 194.33.191.69: offset -25.887976 delay 0.030141, next query 30s
reply from 194.33.191.69: offset -25.871787 delay 0.029909, next query 32s
reply from 212.100.132.50: offset -25.881731 delay 0.023123, next query 30s
reply from 193.125.143.173: offset -25.881964 delay 0.025390, next query 34s
reply from 85.21.125.66: offset -25.838694 delay 0.003271, next query 32s
ntp engine exiting
dispatch_imsg in main: pipe closed
Lost child: child exited
Terminating