public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Lambrecht Jürgen" <J.Lambrecht@TELEVIC.com>
To: ecos <ecos-discuss@ecos.sourceware.org>
Subject: [ECOS] NTP not working when no NTP server available at startup
Date: Fri, 27 Jun 2014 06:36:00 -0000	[thread overview]
Message-ID: <53AD2B74.1040609@televic.com> (raw)

Hi,

we have the problem that NTP is not working when there is no ntp server 
available at startup.

However this is what I read on the ecos pages 
(http://ecos.sourceware.org/docs-3.0/ref/net-sntp-operation.html)

"If SNTP unicast mode is enabled via the CYGPKG_NET_SNTP_UNICAST option, 
the SNTP client can additionally be configured with a list of specific 
NTP servers to query. The general algorithm is as follows: if the system 
clock has not yet been set via an NTP time update, then the client will 
send out NTP requests every 30 seconds to all configured NTP servers. 
Once an NTP time update has been received, the client will send out 
additional NTP requests every 30 minutes in order to update the system 
clock. These requests are resent every 30 seconds until a response is 
received."

We use a list of NTP servers, but we don't see the 30s repeat when a 
server does not answer.

Should this work?

Thanks for any answer,
Jürgen

-- 
Jürgen Lambrecht
R&D Associate
Mobile: +32 499 644 531
Tel: +32 (0)51 303045    Fax: +32 (0)51 310670
http://www.televic-rail.com
Televic Rail NV - Leo Bekaertlaan 1 - 8870 Izegem - Belgium
Company number 0825.539.581 - RPR Kortrijk

--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

             reply	other threads:[~2014-06-27  6:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-27  6:36 Lambrecht Jürgen [this message]
2014-07-28  9:27 ` Lambrecht Jürgen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=53AD2B74.1040609@televic.com \
    --to=j.lambrecht@televic.com \
    --cc=ecos-discuss@ecos.sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).