[ntp:questions] Fwd: Fwd: Re: ntp orphan sync time after boot
Hi Bronto, It seems that i have to speed up the server. It takes 5 minutes before its state(refid) changes from .INIT. to 127.0.0.1 (with ntpq -p on the client). But on the server i have no server defined, only "tos orphan 8" , so i cannot pass iburst. Regards, Rini On 15-01-16 09:40, Marco Marongiu wrote: > On 14/01/16 15:26, Rini van Zetten wrote: >> The problem we have is that it takes about 5 minutes after boot >> before the devices are synchronised. Is there anything possible to >> speed up this process ? > See the burst/iburst options, that should help > > Ciao > -- bronto > ___ > questions mailing list > questions@lists.ntp.org > http://lists.ntp.org/listinfo/questions > -- *Rini van Zetten* /Senior Software Engineer/ - ARVOO Engineering B.V. Tasveld 13 3417 XS Montfoort The Netherlands Tel : 0348-418412 E-mail : r...@arvoo.com <mailto:r...@arvoo.com> Web : www.arvoo.com <http://www.arvoo.com> ** ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
Re: [ntp:questions] ntp orphan sync time after boot
Hi, I overlooked the orphanwait option. Settings this to 0 makes it work like i want. Thanks, Rini On 15-01-16 13:02, Marco Marongiu wrote: > On 15/01/16 12:05, Rini van Zetten wrote: >> It seems that i have to speed up the server. It takes 5 minutes before >> its state(refid) changes from .INIT. to 127.0.0.1 (with ntpq -p on the >> client). >> >> But on the server i have no server defined, only "tos orphan 8" , so i >> cannot pass iburst. > Ah, sorry for the misunderstanding. > > Unfortunately, I have no clue for your case :-( > > Ciao > -- bronto > -- *Rini van Zetten* /Senior Software Engineer/ - ARVOO Engineering B.V. Tasveld 13 3417 XS Montfoort The Netherlands Tel : 0348-418412 E-mail : r...@arvoo.com <mailto:r...@arvoo.com> Web : www.arvoo.com <http://www.arvoo.com> ** ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
[ntp:questions] ntp orphan sync time after boot
Hello, We have several devices connected to each other without internet connection. They have to be synchronised, but the absolute time is not important. I have set up the ntpd on each device in orphan mode with one device as server. This works fine. The problem we have is that it takes about 5 minutes after boot before the devices are synchronised. Is there anything possible to speed up this process ? Thanks, Rini ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
[ntp:questions] ntptime (ntp_gettime) behaviour
Resend Hello, I'm struggling with the behavior of ntptime. Let me first explain what i want to reach. We have an embedded system where we have to log several inputs with timestamp. The timestamp needs to be within 0,5sec accuracy. When using ntp version 4.2.2.p3 I use the output of ntptime to see if we can 'trust' the time on the system. Now i want to upgrade to the newest ntpd (4.2.6p3) because of some issues with dns not available at startup. But with this new version, ntptime give ok status, even when no ntp server have been ever reachable. Is this a bug in the new version, or am i misusing the ntptime output. If so, is there a better way of obtaining the time status of my system? Regards, Rini ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
[ntp:questions] ntptime (ntp_gettime) behaviour
Hello, I'm struggling with the behaviour of ntptime. Let me first explain what i want to reach. We have an embedded system where we have to log several inputs with timestamp. The timestamp needs to be within 0,5sec accuracy. When using ntp version 4.2.2.p3 I use the output of ntptime to see if we can 'trust' the time on the system. Now i want to upgrade to the newest ntpd (4.2.6p3) because of some issues with dns not available at startup. But with this new version, ntptime give ok status, even when no ntp server have been ever reachable. Is this a bug in the new version, or am i misusing the ntptime output. If so, is there a better way of obtaining the time status of my system. Regards, Rini ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
Re: [ntp:questions] nmea and initial large offset
when i start ntpd. But when the clock offset is big (1-1-1970 for example), the ntpd refuses to use the gps reference clock. Using the -g option does not make any difference. Does -g -q -x before starting NTPd as a service not get you there? This does also not work. Thanks all for you input. I'm afraid i have to add a workaround in my application which also gets the gps input, to set the time when it's more then 4 hours away from gps time. Regards, Rini ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
[ntp:questions] nmea and initial large offset
Hello, I'm trying to setup an embedded system with ntpd and a gps device as reference clock. Everyhing went fine when the clock is not too far away when i start ntpd. But when the clock offset is big (1-1-1970 for example), the ntpd refuses to use the gps reference clock. Using the -g option does not make any difference. I'm using ntpd 4.2.6p1 Does anybody know how to setup this ? (i have no lan connection, so an initial ntpdate is no option) Regards, Rini ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
