Alan Gilmour wrote:
We tried installing mbmon and lmmon and healthd, but none seem to work.
How so? Do you have an error message to share with us?
Anyone got any suggestions for other things we can try to detect why
the server is failing? or other ways to check things like CPU temp and
I need something I can run locally to intercept and cache DNS responses.
BIND is not the answer (too heavyweight) and dnsmasq doesn't appear to
cache.
nscd is what I'm used to on Linux but it doesn't seem to be in FreeBSD.
Something called cached but I don't see it on the systems I'm working
Eric F Crist wrote:
I'm trying to use OpenLDAP 2.4, which I installed from the FreeBSD
ports tree. However, everything else I try to install, LDAP support
in Apache22, pam_ldap, seems to want to use 2.3.40 instead.
Obviously, it tries to install that version, which fails since 2.4.7
is
Terry Sposato wrote:
What is the best way to go about getting this exact machine transferred to
the VM? Both machines exist on the same network and will be able to talk to
each other, I have been thinking of a couple of different ways to get all my
data across which is the easy part, but I
Steve Bertrand wrote:
-- Does anyone else have issues in this regard? Particularly, does
anyone else have IPv6 enabled, or better yet in use that can provide any
feedback?
I have a couple of ideas.
First, named has some flags like -4 and -6 (see man named).
Second, firefox has a config flag
I've always used ...
[EMAIL PROTECTED] 550 address poisoned by spammers
or something more descriptive, as it helps the recipient of the bounce
(of the bounce) gets a clue.
On Thu, 2003-05-29 at 07:32, Kirk Strauser wrote:
At 2003-05-29T05:58:05Z, Chuck Swiger [EMAIL PROTECTED] writes:
The secret is starting mysqld with --skip-grant-tables, then resetting.
http://www.mysql.com/doc/en/Resetting_permissions.html
On Wed, 2003-05-28 at 04:06, Frank Tegtmeyer wrote:
Patrick O'Reilly [EMAIL PROTECTED] writes:
I've done like the manuals say (mysqladmin -uroot password xyz), but
I seem to recall that installing (a)apache13+mod_ssl alongside
(b)apache13 caused some messed up situation where the (a) filenames are
different (eg. the httpd binary is named apache and the httpd.conf file
is named apache.conf) apparently to avoid overwriting (b) files. I
highly recommend