On Wed, 16 Jun 2010 10:45:31 +0200
Miroslav Lichvar wrote:
> On Wed, Jun 16, 2010 at 01:27:16PM +0530, J. Bakshi wrote:
> > But it communicates with the local clock unless I give it a restart.
> > Here is a tracking which I observed after 3 hrs from starting my pc.
>
> Are
On Wed, 16 Jun 2010 09:38:33 +0200
Miroslav Lichvar wrote:
> On Tue, Jun 15, 2010 at 07:10:22PM +0530, J. Bakshi wrote:
> > > Maybe the option is in a distribution specific config file used
> > > by the init script? What does "ps a | grep chrony" command say?
> > >
> >
> >
On Wed, Jun 16, 2010 at 01:27:16PM +0530, J. Bakshi wrote:
> But it communicates with the local clock unless I give it a restart.
> Here is a tracking which I observed after 3 hrs from starting my pc.
Are the servers in "chronyc activity" output offline? Or are they
missing?
If they are offline,
On Tue, Jun 15, 2010 at 07:10:22PM +0530, J. Bakshi wrote:
> > Maybe the option is in a distribution specific config file used by the
> > init script? What does "ps a | grep chrony" command say?
> >
>
> Big Surprising !!!
>
> After a reboot I have checked as you suggested and I got
>
>
On Tue, 15 Jun 2010 15:24:30 +0200
Miroslav Lichvar wrote:
> On Mon, Jun 14, 2010 at 02:25:12PM +0530, J. Bakshi wrote:
> > > > Jun 14 12:22:28 debian chronyd[5190]: Could not open dump
> > > > file /var/lib/chrony/202.169.224.16.dat Jun 14 12:22:28 debian
> > > >
On Mon, Jun 14, 2010 at 02:25:12PM +0530, J. Bakshi wrote:
> > > Jun 14 12:22:28 debian chronyd[5190]: Could not open dump
> > > file /var/lib/chrony/202.169.224.16.dat Jun 14 12:22:28 debian
> > > chronyd[5190]: Could not open dump
> > > file /var/lib/chrony/158.108.212.149.dat
> > >
> > > I
On Mon, 14 Jun 2010 09:44:30 +0200
Miroslav Lichvar wrote:
> On Mon, Jun 14, 2010 at 12:37:42PM +0530, J. Bakshi wrote:
> > Jun 14 12:22:28 debian chronyd[5190]: Could not open dump
> > file /var/lib/chrony/202.169.224.16.dat Jun 14 12:22:28 debian
> > chronyd[5190]: Could