Thanks as well to both of you. I too learned something new.
Scott Robbins wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, Feb 04, 2005 at 01:41:39PM -0800, Kevin Oberman wrote:
Date: Fri, 4 Feb 2005 16:29:03 -0500
From: Scott Robbins <[EMAIL PROTECTED]>
Sender: [EMAIL PROTECTED]
--
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, Feb 04, 2005 at 01:41:39PM -0800, Kevin Oberman wrote:
> > Date: Fri, 4 Feb 2005 16:29:03 -0500
> > From: Scott Robbins <[EMAIL PROTECTED]>
> > Sender: [EMAIL PROTECTED]
> >
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA1
> >
> >
> > T
> Date: Fri, 4 Feb 2005 16:29:03 -0500
> From: Scott Robbins <[EMAIL PROTECTED]>
> Sender: [EMAIL PROTECTED]
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Fri, Feb 04, 2005 at 01:18:26PM -0800, Stan wrote:
> > Hmmm. My rc.conf has ntpd_enable-"YES", but not ntpdate_enable="YES".
> >
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, Feb 04, 2005 at 01:18:26PM -0800, Stan wrote:
> Hmmm. My rc.conf has ntpd_enable-"YES", but not ntpdate_enable="YES".
> Thanks!
They do conflict with each other, I'm not sure what will happen if you
have both in rc.conf. Hopefully ntpdate wi
Hmmm. My rc.conf has ntpd_enable-"YES", but not ntpdate_enable="YES".
Thanks!
Dan Nelson wrote:
In the last episode (Feb 04), Stan said:
I ran into this same problem. After trying various things, I finally
gave up and did it the easy way. If you don't mind rebooting, the
easiest thing to do i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, Feb 04, 2005 at 01:47:53PM -0600, Dan Nelson wrote:
> In the last episode (Feb 04), Stan said:
> > I ran into this same problem. After trying various things, I finally
> > gave up and did it the easy way. If you don't mind rebooting, the
> >
In the last episode (Feb 04), Stan said:
> I ran into this same problem. After trying various things, I finally
> gave up and did it the easy way. If you don't mind rebooting, the
> easiest thing to do is set the clock in the BIOS as accurately as
> possible, then let ntpd fine tune it from there
I ran into this same problem. After trying various things, I finally
gave up
and did it the easy way. If you don't mind rebooting, the easiest thing to
do is set the clock in the BIOS as accurately as possible, then let ntpd
fine tune it from there.
Regards,
Stan
Marco van Lienen wrote:
On Thu,
On Fri, 4 Feb 2005, Marco van Lienen wrote:
> On Thu, Feb 03, 2005 at 06:03:48PM -, Rob MacGregor wrote:
> >
> > Not within NTPd itself. You could go with manually stepping the time in 1s
> > intervals. It's either that or drop the securelevel in rc.conf and reboot
> > (then
> > reset the s
On Friday, February 04, 2005 4:14 PM, Marco van Lienen <> unleashed the infinite
monkeys and produced:
> Isn't there a tool like hwclock for Linux?
adjkerntz
Don't have a FreeBSD box to reboot to find out whether it runs at startup and
shutdown by default though.
--
Rob | Oh my God! They kille
On Thu, Feb 03, 2005 at 06:03:48PM -, Rob MacGregor wrote:
>
> Not within NTPd itself. You could go with manually stepping the time in 1s
> intervals. It's either that or drop the securelevel in rc.conf and reboot
> (then
> reset the securelevel).
>
> Of course, you probably want to make s
Sorry for replying to myself ...
Oliver Fromme <[EMAIL PROTECTED]> wrote:
> Adding to that, the following /bin/sh snippet should do
> (untested!). You have to kill ntpd before.
>
> STEP=100# number of seconds to step forward
> while [ $STEP -gt 0 ]; do
> date -f %s $(( `dat
Rob MacGregor <[EMAIL PROTECTED]> wrote:
> Eli K. Breen wrote:
> > I'm not sure that this will cut it as it will days a very long time to
> > adjust to the proper time. Is there any way to speed this up?
>
> Not within NTPd itself. You could go with manually stepping the time in 1s
> interv
On Thursday, February 03, 2005 5:57 PM, Eli K. Breen <> unleashed the infinite
monkeys and produced:
> I'm not sure that this will cut it as it will days a very long time to
> adjust to the proper time. Is there any way to speed this up?
Not within NTPd itself. You could go with manually steppin
I'm not sure that this will cut it as it will days a very long time to
adjust to the proper time. Is there any way to speed this up?
-E-
David Magda wrote:
On Feb 2, 2005, at 16:56, Eli K. Breen wrote:
Lastly this machine is in production and cannot be rebooted.
Stop the NTP daemon and restart i
Eli K. Breen <[EMAIL PROTECTED]> wrote:
> I'm running in to an issue where I can't set the clock on a machine
> because the secure level was bumped to 2 before the clock was set.
> Unfortunately adjustments are now clamped to < 1s. Is there any way I
> can force ntpd to adjust the clock by
On Feb 2, 2005, at 16:56, Eli K. Breen wrote:
Lastly this machine is in production and cannot be rebooted.
Stop the NTP daemon and restart it so that it uses the "-x" option.
From ntpd(8):
-x Normally, the time is slewed if the offset is less than
the step
threshold, which
I'm running in to an issue where I can't set the clock on a machine
because the secure level was bumped to 2 before the clock was set.
Unfortunately adjustments are now clamped to < 1s. Is there any way I
can force ntpd to adjust the clock by say, 1s every two seconds or at
least something mor
18 matches
Mail list logo
