pigeon wrote:
On Thu, Oct 02, 2003 at 11:28:12PM +0100, Ben Edwards wrote:
On my laptop, I've added the -g switch to ntpd's startup, so the first
time it syncs, it forcibly resets to the NTP time if that's out of
bounds. Doing this involved editing /etc/init.d/ntp-simple and adding
'-- -g' to
On my laptop, I've added the -g switch to ntpd's startup, so the first
time it syncs, it forcibly resets to the NTP time if that's out of
bounds. Doing this involved editing /etc/init.d/ntp-simple and adding
'-- -g' to the end of the start-stop-daemon lines that start ntpd.
This is
On Thu, Oct 02, 2003 at 11:28:12PM +0100, Ben Edwards wrote:
On my laptop, I've added the -g switch to ntpd's startup, so the first
time it syncs, it forcibly resets to the NTP time if that's out of
bounds. Doing this involved editing /etc/init.d/ntp-simple and adding
'-- -g' to the end
I have a box which will not keep the time. Every time I shut it down it
looses the time and goes back to 1980. I thought ntpd was the answer
but as the difference between the system(pc) and the actual(ntp) time is
so great it won't work.
So how can I get ntpd to set time WHATEVER the system
Ben Edwards wrote:
I have a box which will not keep the time. Every time I shut it down it
looses the time and goes back to 1980. I thought ntpd was the answer
but as the difference between the system(pc) and the actual(ntp) time is
so great it won't work.
So how can I get ntpd to set time
Ben Edwards wrote:
So how can I get ntpd to set time WHATEVER the system time is,
regardless if it is 1980.
Try using ntpdate instead - it can brutally change your system time
right away, rather than trying to neatly slew it.
John
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a
Ben writes:
So how can I get ntpd to set time WHATEVER the system time is, regardless
if it is 1980.
Ntp won't change the system clock if it is too far off. Use ntpdate to set
the clock at bootup and then start ntp.
--
John Hasler
[EMAIL PROTECTED] (John Hasler)
Dancing Horse Hill
Elmwood, WI
Have already replaced the bios battery and it still douse not work.
think there is something up with the motherboard.
Greg Bolshaw wrote:
Ben Edwards wrote:
I have a box which will not keep the time. Every time I shut it down it
looses the time and goes back to 1980. I thought ntpd was the
Ben Edwards [EMAIL PROTECTED] writes:
I have a box which will not keep the time. Every time I shut it down it
looses the time and goes back to 1980. I thought ntpd was the answer
but as the difference between the system(pc) and the actual(ntp) time is
so great it won't work.
So how can I
Ben Edwards wrote:
Greg Bolshaw wrote:
Ben Edwards wrote:
I have a box which will not keep the time. Every time I shut it
down it
looses the time and goes back to 1980
Why not just replace the BIOS battery? That way you won't lose the
time when you shutdown.
Have already replaced the bios
On Wed, Oct 01, 2003 at 08:13:28AM -0500, John Hasler wrote:
| Ben writes:
| So how can I get ntpd to set time WHATEVER the system time is, regardless
| if it is 1980.
|
| Ntp won't change the system clock if it is too far off. Use ntpdate
| to set the clock at bootup and then start ntp.
How
Derrick writes:
How can this be done with chrony?
With a chonyc makestep command.
--
John Hasler
[EMAIL PROTECTED] (John Hasler)
Dancing Horse Hill
Elmwood, WI
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
12 matches
Mail list logo