Thanks a lot John.
On Thu, 19 Aug 2010 10:10:28 -0500
John Hasler wrote:
> Add the line
>
> sleep 1
>
> after line 54 of /etc/init.d/chrony, which reads:
>
> start-stop-daemon --start --verbose --exec $DAEMON || { echo "$DAEMON
> already running.";
> exit
On Thu, 19 Aug 2010 10:42:59 +0200
Miroslav Lichvar wrote:
> On Thu, Aug 19, 2010 at 10:20:10AM +0200, Miroslav Lichvar wrote:
> > On Thu, Aug 19, 2010 at 01:02:03PM +0530, J. Bakshi wrote:
> > > OK, thanks a lot for the clarification. I'll set a daemon then which
> > >
OK, thanks a lot for the clarification. I'll set a daemon then which check the
presence of internet and then restart chrony.
Thanks once again
On Wed, 18 Aug 2010 23:43:39 -0700 (PDT)
Bill Unruh wrote:
> Sorry, did not see it. It seems to me that your network is coming
On Thu, Aug 19, 2010 at 10:20:10AM +0200, Miroslav Lichvar wrote:
> On Thu, Aug 19, 2010 at 01:02:03PM +0530, J. Bakshi wrote:
> > OK, thanks a lot for the clarification. I'll set a daemon then which
> > check the presence of internet and then restart chrony.
>
> You might also want to try the
On Thu, Aug 19, 2010 at 01:02:03PM +0530, J. Bakshi wrote:
> OK, thanks a lot for the clarification. I'll set a daemon then which
> check the presence of internet and then restart chrony.
You might also want to try the latest git version, it retries name
resolving until it gets a non-temporary
Add the line
sleep 1
after line 54 of /etc/init.d/chrony, which reads:
start-stop-daemon --start --verbose --exec $DAEMON || { echo "$DAEMON
already running."; exit 1; }
--
John Hasler
jhas...@newsguy.com
Elmwood, WI USA
---
To unsubscribe email
Sorry, did not see it. It seems to me that your network is coming up long
after chrony does, leading to the offline behaviour. Note that without a
network, it cannot even figure out what 0.asia.pool.ntp is so cannot even try
to connect.
You could try to set up one server at least with IP rather
Hello list,
This is a debian squeeze box, chrony version 1.24
`
#chronyc -v
chronyc (chrony) version 1.24
``
chrony is already included in run-level, but after boot, "chronyc tracking"
reports
#chronyc tracking
Reference ID:
It looks like chrony is coming up long before your netwrk is. What's your
chrony.conf like?
On Wed, 18 Aug 2010, J. Bakshi wrote:
Hello list,
This is a debian squeeze box, chrony version 1.24
`
#chronyc -v
chronyc (chrony) version 1.24
``
chrony is