After poking about vmware's web site I've done the
following.
Installed VMWare tools for FreeBSD and activated it.
Also, from the toolbox I checked of sync clock.
Not yet implemented: /boot/loader.conf and disabling
APIC. I'll try this later.
__
Just a follow up,
Turned off NTPD and the clock is still drifting.
I set the clock around 1200 on Dec 7th, and the time
is reported as Dec 7th 22:20 PST 2006.
Have a burning question?
Go to www.Answers.ya
--- John Webster <[EMAIL PROTECTED]> wrote:
>
>
> --On Friday, December 01, 2006 10:23:17 -0800 Chuck
> Swiger <[EMAIL PROTECTED]> wrote:
>
> > On Dec 1, 2006, at 9:56 AM, Kris Anderson wrote:
> >> Darn the system time strayed over night. One
> thing I
> >> failed to mention is that freebsd is
--- "Peter A. Giessel" <[EMAIL PROTECTED]> wrote:
>
>
> On 2006/12/01 8:56, Kris Anderson seems to have
> typed:
> > --- Chuck Swiger <[EMAIL PROTECTED]> wrote:
> >> However, if you are dual-booting between FreeBSD
> and
> >> Windows, you
> >> will also need to consider whether to keep the
> >
--On Friday, December 01, 2006 10:23:17 -0800 Chuck Swiger <[EMAIL PROTECTED]>
wrote:
> On Dec 1, 2006, at 9:56 AM, Kris Anderson wrote:
>> Darn the system time strayed over night. One thing I
>> failed to mention is that freebsd is running on a
>> virtual machine.
>
> Sigh-- you're right, you
On Dec 1, 2006, at 9:56 AM, Kris Anderson wrote:
Darn the system time strayed over night. One thing I
failed to mention is that freebsd is running on a
virtual machine.
Sigh-- you're right, you should have mentioned this before.
One should not attempt to change the clock from within a virtual
On 2006/12/01 8:56, Kris Anderson seems to have typed:
> --- Chuck Swiger <[EMAIL PROTECTED]> wrote:
>> However, if you are dual-booting between FreeBSD and
>> Windows, you
>> will also need to consider whether to keep the
>> CMOS/BIOS clock
>> running in UTC or in your local timezone; see "m
--- Chuck Swiger <[EMAIL PROTECTED]> wrote:
> On Nov 30, 2006, at 12:55 PM, Kris Anderson wrote:
> >> Your clock is off by a little over an hour; while
> >> ntpd can correct very large offsets, doing so
> takes a long time.
> >> Kill ntpd, re-run "ntpdate -b", double-check that
> your clock is sa
On Nov 30, 2006, at 12:55 PM, Kris Anderson wrote:
Your clock is off by a little over an hour; while
ntpd can correct very large offsets, doing so takes a long time.
Kill ntpd, re-run "ntpdate -b", double-check that your clock is sane,
and then re-start ntpd.
Off by an hour? Let's see the date
--- "Peter A. Giessel" <[EMAIL PROTECTED]> wrote:
> On 2006/11/30 11:16, Kris Anderson seems to have
> typed:
> > Here's the output from ntpq.
> >
> > webdev# ntpq -p
> > remote refid st t when poll
> reach
> > delay offset jitter
> >
>
==
--- Chuck Swiger <[EMAIL PROTECTED]> wrote:
> On Nov 30, 2006, at 12:16 PM, Kris Anderson wrote:
> > Here's the output from ntpq.
> >
> > webdev# ntpq -p
> > remote refid st t when poll
> reach
> > delay offset jitter
> >
>
=
On 2006/11/30 11:48, Peter A. Giessel seems to have typed:
> On 2006/11/30 11:16, Kris Anderson seems to have typed:
>> Here's the output from ntpq.
>>
>> webdev# ntpq -p
>> remote refid st t when poll reach delay offset
>> jitter
>> ===
On 2006/11/30 11:16, Kris Anderson seems to have typed:
> Here's the output from ntpq.
>
> webdev# ntpq -p
> remote refid st t when poll reach
> delay offset jitter
> ==
> time-a.nist.gov .ACTS.
On Nov 30, 2006, at 12:16 PM, Kris Anderson wrote:
Here's the output from ntpq.
webdev# ntpq -p
remote refid st t when poll reach
delay offset jitter
==
time-a.nist.gov .ACTS. 1 u 4
--- Chuck Swiger <[EMAIL PROTECTED]> wrote:
> On Nov 30, 2006, at 11:16 AM, Kris Anderson wrote:
> > I first ran ntpdate from /etc/rc.d/ntpdate and
> that
> > set the date and time.
>
> Good. That should have gotten your clock reasonably
> sync'ed.
>
> > Then I ran /etc/rc.d/ntpd and that star
On Nov 30, 2006, at 11:16 AM, Kris Anderson wrote:
I first ran ntpdate from /etc/rc.d/ntpdate and that
set the date and time.
Good. That should have gotten your clock reasonably sync'ed.
Then I ran /etc/rc.d/ntpd and that started up fine.
The followind day I find that the system still think
Hi folks,
Having an issue with ntpd not keeping the correct
time.
I first ran ntpdate from /etc/rc.d/ntpdate and that
set the date and time.
Then I ran /etc/rc.d/ntpd and that started up fine.
The followind day I find that the system still thinks
it is the previous day and such.
I thought the p
17 matches
Mail list logo
