on Mon, Sep 24, 2001 at 07:04:05PM -0400, Doug Fields ([EMAIL PROTECTED]) wrote:
>
> > > I then restart the ntp daemon and noticed my date never changed.
> > > However, earlier, I used ntpdate to sync with that time server
> > > and it worked. (I make sure both aren't running at the same time)
> >
What you're looking for if you want a quick "set the time right now"
application is ntpdate, not ntp. NTP slews the clock and also sets up
settings to know how good/bad your internal clock are. Messing with the
software clock while using NTP is just going to make NTP take even
longer to figure ou
> I then restart the ntp daemon and noticed my date never changed.
> However, earlier, I used ntpdate to sync with that time server
> and it worked. (I make sure both aren't running at the same time)
Have you tried running ntp recently? Often the time difference is too
great for ntp to sync in
Thanks to those who replied.
What I would do is change my date to a few hours earlier than
normal time, and then launch ntp.
I was under the impression it would sync quickly.
I wonder how long would I have to wait for it sync up?
I checked with ntpq and ran "peers", there was alot of info from
th
On Mon, Sep 24, 2001 at 01:19:54PM -0700, Mike Egglestone wrote:
> Hi,
>
> I thought I would try and sync my potato server
> to an internet time server, so I installed ntp, edited
> the /etc/ntp.conf file:
>
> server 192.5.41.209
>
> I then restart the ntp daemon and noticed my date never chang
Hi,
I thought I would try and sync my potato server
to an internet time server, so I installed ntp, edited
the /etc/ntp.conf file:
server 192.5.41.209
I then restart the ntp daemon and noticed my date never changed.
However, earlier, I used ntpdate to sync with that time server
and it worked.
6 matches
Mail list logo
