David Robillard wrote:
Basically the only reason I have for using VM Tools is for the ability
of Vmotion and such with our ESX Server farm. It's really the only
benefit that the VM tools will give me on FreeBSD as all my virtual
machines which are running FreeBSD are servers and don't use any
I wrote a shell script to email me the output of ntpdc -p and put it in my
crontab.
It works for a week, and at some point over the weekend my script loses its
executable permissions for me (user) but not for group or other.
Is there a FreeBSD periodic job that runs periodically and removes
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
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 running
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
My primary FreeBSD box is a Dual P3 700 Mhz, which is dandy for my
console mode server usage but kind of blows for buildworld and kernels
when I want them done a timely fashion. I'd like to do it in a
dual-proc VM on my quad core workstation, where it gets done a lot faster.
Is there any
[EMAIL PROTECTED] wrote:
It is /usr/obj you want to mount across, though it
will work. Assuming they're similar enough
versions. Also assure yourself that their respective
/etc/make.conf (and/or /etc/src.conf) files are
essentially identical, or you will great sorrows
have.
I'm not that
Brent Jones wrote:
What you propose works fine, but you should have the /usr/src and
/usr/obj directories locally stored on your fast machine for the builds.
Then have your slow machine nfs mount /usr/src and /usr/obj from your
fast machine, and simply do your make installs from your slow
NetOpsCenter wrote:
I have 5 of the nic cards TEG PCI TXR running on Various versions of
7. * and 8.* of FreeBSD.
There was somebody on the weekind also having trouble with version 6.*
Same as your problem.
Try switch to 7.*
At this point, switching to 7.* isn't really an option and its
NetOpsCenter wrote:
I have 5 of the nic cards TEG PCI TXR running on Various versions of
7. * and 8.* of FreeBSD.
There was somebody on the weekind also having trouble with version 6.*
Same as your problem.
Try switch to 7.*
Now I see why -- the code looks way overhauled recently (like
Went looking for a cheap GigE PCI card to use with a 6.2
(6.3-PRERELEASE) stable system, and brought this home due to Microcenter
not stocking Intel cards and me not wanting to wait for Newegg to ship
one to me.
I have the re driver built into the kernel, but this particular card is
not
Shawn Barnhart wrote:
Went looking for a cheap GigE PCI card to use with a 6.2
(6.3-PRERELEASE) stable system, and brought this home due to
Microcenter not stocking Intel cards and me not wanting to wait for
Newegg to ship one to me.
Card works after switching slots on the motherboard, but I
Michal F. Hanula wrote:
Your postfix is trying to use saslauthd, which usually listens on
/var/run/saslauthd/mux. The right way to fix this depends on whether
you want to use saslauthd and the place you store your e-mail user data.
I want authentication against /etc/passwd (ultimately), not
Paul Schmehl wrote:
It should, because it calls this:
.if defined(WITH_SASL2)
LIB_DEPENDS+= sasl2.2:${PORTSDIR}/security/cyrus-sasl2
POSTFIX_CCARGS+=-DUSE_SASL_AUTH -DUSE_CYRUS_SASL
-I${LOCALBASE}/include -I${LOCALBASE}/include/sasl
POSTFIX_AUXLIBS+= -L${LOCALBASE}/lib
I'm running a recently built 6.2 stable build (which uname calls
6.3-PRERELEASE) and
Postfix built from ports with the Cyrus SASLv2 option. Postfix works
fine, including TLS but SASAL authentication logs file not found errors.
Jan 9 17:14:10 postfix postfix/smtpd[48488]: warning: SASL
15 matches
Mail list logo
