because it breaks teh standard and teh networking guru's don't like it.
Basically in the face of broken clients, (read PCs) the TCP protocol
can gather an unacceptable collection of fin-wait-2 sessions. THis is in
the way the protocol was designed. To reduce it we revert to fin-wait-1
and resent
From: Julian Elischer [mailto:[EMAIL PROTECTED]]
>I have a patch to fix the fin-wait-2 problem..
Any reason this could't be applied to -stable with a corresponding sysctl
variable?
Charles
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the mes
> "Min Wei (Exchange)" wrote:
>
> Hi. I am confused at the following strange FreeBSD reboot case.
> I have a Dell PowerEdge 2300 dual proc machine with Intel 100/10
> netcard.
> I put 3.2 SMP kernel with options MAXUSERS=256 and
> NMBCLUSTERS=32768.
Try some rational numbers. Get that NMBCLUSTER
Title: FreeBSD reboots every 45 minutes
Hi. I am confused at the following strange FreeBSD reboot case.
I have a Dell PowerEdge 2300 dual proc machine with Intel 100/10 netcard.
I put 3.2 SMP kernel with options MAXUSERS=256 and NMBCLUSTERS=32768.
Otherwise kernel is almost the same as the
roc with 512M RAM. I recompiled the
> kernel
> with SMP options and set MAXMEM to 512M (since by default FreeBSD thinks it
> only
> has 64M). I have apache installed as the Web server.
>
> However during our Web stress run, FreeBSD reboots periodically. I wonder
> if it'
default FreeBSD thinks it
only
has 64M). I have apache installed as the Web server.
However during our Web stress run, FreeBSD reboots periodically. I wonder
if it's because a lot of TCP connections at FIN_WAIT_2 state, which causes
the kernel crash. The load on the machine is not high (CPU is
6 matches
Mail list logo
