Date: Wed, 05 May 1999 19:50:05 -0400 (EDT) From: Seth <seth@freebie.dp.ny.frb.org> To: freebsd-stable@FreeBSD.ORG Subject: Re: Fun with TCP. Message-ID: <Pine.BSF.4.10.9905051945390.789-100000@freebie.dp.ny.frb.org> In-Reply-To: <Pine.BSF.4.10.9905051821260.295-100000@freebie.dp.ny.frb.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Sorry to follow up on my own post. Just thought I'd share this. It turns out that whatever was causing the kernel to panic went away after I limited kern.maxprocperuid to 250 for the users ( it had been 1043, with maxproc set at 1044). So this problem seems to have moved. I'm not sure it's significant at this point, but if someone is interested in pursuing it, I'll be happy to take whatever traces you need if you send me some mail. I'm fairly confident I can reproduce it if maxprocperuid is set back to (maxproc-1). SB On Wed, 5 May 1999, Seth wrote: > I used the "bounce" utility to redirect localhost:3737 to localhost:3838, > and localhost:3838 back to localhost:3737 just to see what would happen. > > (ok, I have too much time on my hands :)) > > Everything was fine until I telnetted to 3737. I expected SOMETHING to > happen, but I'm not sure why it was this severe (any user can do this): > > Kernel paniced, trap 12. It's reproduceable on all my systems, so I won't > dump a whole bunch of info here (if you want it, let me know). > > uname: > 3.1-STABLE FreeBSD 3.1-STABLE #0: Tue Apr 27 14:41:30 EDT 1999 > > > Does this stuff go to this list, or should I send-pr? > > SB > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.10.9905051945390.789-100000>