On Thu, 08 Apr 2004, Pigeon wrote:
> On Wed, Apr 07, 2004 at 08:30:29PM -0700, William Ballard wrote:
> > On Thu, Apr 08, 2004 at 05:04:46AM +0200, Christian Schnobrich wrote:
> > > IIRC, ntpdate (and ntpd and chrony) will not set your clock if it is off
> > > by too much. I think by default it is
On Wed, Apr 07, 2004 at 08:30:29PM -0700, William Ballard wrote:
> On Thu, Apr 08, 2004 at 05:04:46AM +0200, Christian Schnobrich wrote:
> > IIRC, ntpdate (and ntpd and chrony) will not set your clock if it is off
> > by too much. I think by default it is 1 hour (3600 sec) for all three of
> > them
On Wed, Apr 07, 2004 at 11:47:50PM -0600, Bob Proulx wrote:
> Best not to run ntpdate to step the clock while ntpd is running or
> confusion would result. So stop ntpd first and start it again
> afterward.
...in fact, you have to stop ntpd, or else ntpdate won't work.
--
Pigeon
Be kind to pige
On Thu, 08 Apr 2004, Kirk Strauser wrote:
> At 2004-04-08T03:04:46Z, Christian Schnobrich <[EMAIL PROTECTED]> writes:
> > Oh, and... everybody suggests chrony as a far superior and more stable
> > solution than ntpd.
For certain situations, yes. Chrony is much better for high latency,
inconstant
* Kirk Strauser <[EMAIL PROTECTED]> [040408 09:05]:
>
> I occasionally hear someone say that chrony is better than ntpd, but
> I've never heard the reasons why.
I tried setting up ntp and found it difficult, but tried setting up
chrony and found it easy. Since I'm just running a few boxes at h
At 2004-04-08T03:04:46Z, Christian Schnobrich <[EMAIL PROTECTED]> writes:
> Oh, and... everybody suggests chrony as a far superior and more stable
> solution than ntpd.
More stable? In what way? Not once in the years that I've used ntpd have I
ever had problems with it.
I occasionally hear som
Chris Horn wrote:
> cc: me on your reply, as I'm not subscribed)!
> Running '/etc/init.d/ntpdate start' does not fix the problem.
What do the logs say in /var/log/syslog?
I suspect you have a firewall in the way.
Try running ntpdate interactively.
/etc/init.d/ntp stop# or /etc/init.d/ntp
On Thu, Apr 08, 2004 at 05:04:46AM +0200, Christian Schnobrich wrote:
> IIRC, ntpdate (and ntpd and chrony) will not set your clock if it is off
> by too much. I think by default it is 1 hour (3600 sec) for all three of
> them.
ntpdate just adjusted my clock which was off by 3602 seconds
7 Apr 1
On Thursday 08 April 2004 03:04 am, Christian Schnobrich wrote:
>I can merely point you to the (quite exhaustive) documentation you get
>when installing ntp-doc. As quick fix, you may manually set the time to
>something that's reasonably close and re-run ntpdate.
Sorry, this just doesn't work.
A
On Don, 2004-04-08 at 04:20, Chris Horn wrote:
> Okay, I'm completely lost on this one. I have one box that can't tell time
> and I don't know what's the matter with it.
>
> when UTC is around Thu Apr 8 02:16:20 UTC 2004, this machine reports:
>
> # date -u && date
> Wed Apr 7 22:16:37 UTC 200
On Thursday 08 April 2004 02:20 am, Chris Horn wrote:
>Okay, I'm completely lost on this one. I have one box that can't tell time
>and I don't know what's the matter with it.
>
>when UTC is around Thu Apr 8 02:16:20 UTC 2004, this machine reports:
>
># date -u && date
>Wed Apr 7 22:16:37 UTC 200
Okay, I'm completely lost on this one. I have one box that can't tell time
and I don't know what's the matter with it.
when UTC is around Thu Apr 8 02:16:20 UTC 2004, this machine reports:
# date -u && date
Wed Apr 7 22:16:37 UTC 2004
Wed Apr 7 18:16:37 EDT 2004
# hwclock --show --utc
Wed Ap
12 matches
Mail list logo
