Any idea why a growfs to this size works
growfs: 493962.0MB (1011634176 sectors) block size 16384, fragment size
2048
using 2688 cylinder groups of 183.77MB, 11761 blks, 23552
inodes.
with soft updates
super-block backups (for fsck -b #) at:
1010881632, 1011257984
but a growfs t
I'm running a FreeBSD 5.3-p5 server and several FreeBSD 4.11 clients.
The clients run high levels of concurrency (web servers running several
hundred processes at a time). The clients NFS connection tend to lockup
when running nfsiod but (so far) appear not to when not running nfsiod.
When the
On Feb 11, 2005, at 6:14 PM, Anthony Atkielski wrote:
Chad Leigh -- Shire.Net LLC writes:
And the standard answer is RTFM
I don't know of anything in the manuals or on the Web site that answers
this type of question.
This is a mailing list for questions about how to use FreeBSD, not why
you should
On Jan 28, 2005, at 4:36 PM, Chuck Swiger wrote:
Michael E.Conlen wrote:
I'm using FreeBSD and PF as a firewall between two networks. I want
to change the MTU on one network to 9k but I have to leave the MTU on
the other network at 1500 bytes. Will the system handle the
fragmenting for me going
I'm using FreeBSD and PF as a firewall between two networks. I want to
change the MTU on one network to 9k but I have to leave the MTU on the
other network at 1500 bytes. Will the system handle the fragmenting for
me going from the larger MTU to the smaller?
--
Michael Conlen
_
On Sep 28, 2004, at 8:33 AM, shane mullins wrote:
Why not just run OpenBSD if you want to use pf? I use both Free
and OpenBSD. But, pf is much easier to set up on OpenBSD. Just
install OpenBSD, enable routing, enable pf in rc.conf and you are
done.
I can tell you in my case OpenBSD doesn'
You patch the open() call in the kernel to log messages to syslog. I've
got patches for the kernel to log exec() but not open(). It's fairly
trivial once you see it in action.
--
Michael Conlen
On Oct 27, 2003, at 6:35 AM, Matthew Seaman wrote:
On Mon, Oct 27, 2003 at 11:57:31AM +0800, [EMAIL P
For FreeBSD I recommend the Net-SNMP package www.net-snmp.org. It's a very
good package, highly extensible, and generally reliable.
Be sure to configure it properly so that it's secure. change the community
string, and restrict what IP addresses can access it. Use SNMP v3 if at all
possible.
--
M
