Gelsema, P (Patrick) wrote:
I am having problems with the vmware tools. It seems to die, everytime
when I start it or rebooted.
Feb 10 13:22:25 wolverine kernel: pid 566 (vmware-checkvm), uid 0: exited
on sig
nal 12 (core dumped)
$ uname -a
FreeBSD wolverine.superhero.nl 7.0-RC2 FreeBSD 7.0-RC2
On Sat, February 9, 2008 20:40, Peter Boosten wrote:
> Quoting Shawn Barnhart <[EMAIL PROTECTED]>:
>
>
>> When you installed the tools, did they require X to be operational?
>> I'm not planning on running X.
>>
> Neither am I, so no X here.
I am having problems with the vmware tools. It seems to d
Quoting Shawn Barnhart <[EMAIL PROTECTED]>:
When you installed the tools, did they require X to be operational?
I'm not planning on running X.
Neither am I, so no X here.
Peter
--
http://www.boosten.org
___
freebsd-questions@freebsd.org mailing lis
Peter Boosten wrote:
In my /boot/loader.conf:
kern.hz="100"
I rebuilt the kernel with options HZ=100 and this seems to "fix" it --
ntpd sync'd immediately and the clock does not appear to drift.
When you installed the tools, did they require X to be operational? I'm
not planning on runni
Quoting Shawn Barnhart <[EMAIL PROTECTED]>:
I know this is a major nuisance, but I can't remember how I dealt with
it in the past. My most recent stab at using ntpd with minpoll 4
polling of a local ntp time source isn't working, the clock drift
prevents any sync from happening (but I'll admit
I know this is a major nuisance, but I can't remember how I dealt with
it in the past. My most recent stab at using ntpd with minpoll 4
polling of a local ntp time source isn't working, the clock drift
prevents any sync from happening (but I'll admit not trying some of the
more aggressive time
