From owner-freebsd-hackers  Mon Oct 11 14:30: 1 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145])
	by hub.freebsd.org (Postfix) with ESMTP id 771AC14C36
	for <freebsd-hackers@FreeBSD.ORG>; Mon, 11 Oct 1999 14:29:56 -0700 (PDT)
	(envelope-from mike@dingo.cdrom.com)
Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1])
	by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id OAA02032;
	Mon, 11 Oct 1999 14:20:08 -0700 (PDT)
	(envelope-from mike@dingo.cdrom.com)
Message-Id: <199910112120.OAA02032@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: Andy Farkas <andyf@speednet.com.au>
Cc: Mike Smith <mike@smith.net.au>,
	Chris Costello <chris@calldei.com>, freebsd-hackers@FreeBSD.ORG
Subject: Re: aio_read kills machine 
In-reply-to: Your message of "Tue, 12 Oct 1999 07:22:47 +1000."
             <Pine.BSF.4.10.9910120720450.3838-100000@localhost> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 11 Oct 1999 14:20:08 -0700
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> 
> On Mon, 11 Oct 1999, Mike Smith wrote:
> 
> > > Running ``nmap -sP 172.22.0.0/16'' as a normal user will cause a panic on
> > > a recent 3.3-STABLE system :(
> > 
> > Could you be any less specific about the panic?  Any sort of detail is 
> > just going to make us want to fix it.
> 
> Here most of the message I posted to -stable:

Oh, that one.  You need to increase maxusers or NMBCLUSTERS.  This is 
the subject of ongoing work in -current that ought to make it back to 
-stable eventually.

> ----snip----
> *From andyf@speednet.com.au Tue Oct 12 07:20:08 1999
> Date: Mon, 27 Sep 1999 19:43:21 +1000 (EST)
> To: freebsd-stable@FreeBSD.ORG
> Subject: nmap V. 2.3BETA5 causes panic
> 
> The system will panic with an 'out of mbufs' message when I run the above
> nmap command ("ping scan" a class B subnet - my internal IP network).
> 
> Should this be happening when run as a normal user??  The kernel is pretty
> stock with maxusers 32, no NMBCLUSTERS option, unneeded devices removed.  
> There is 64M RAM and 256M swap; it is has dual 90MHz P54C's.
> 
> This system (my workstation) is a:
> FreeBSD 3.3-STABLE #0: Mon Sep 20 09:44:35 EST 1999
> 
> I am:
> bash-2.03$ id
> uid=1000(andyf) gid=1000(andyf) groups=1000(andyf), 0(wheel)
> 
> I have:
> bash-2.03$ limits
> Resource limits (current):
>   cputime          infinity secs
>   filesize          1048576 kb
>   datasize            65536 kb
>   stacksize            8192 kb
>   coredumpsize       131072 kb
>   memoryuse           65536 kb
>   memorylocked         8192 kb
>   maxprocesses          256
>   openfiles             256
> 
> I use:
> bash-2.03$ 
> 
> How would you go about preventing this problem?
> 
> Thanks.
> ----snip----
> 
> > 
> > -- 
> > \\ Give a man a fish, and you feed him for a day. \\  Mike Smith
> > \\ Tell him he should learn how to fish himself,  \\  msmith@freebsd.org
> > \\ and he'll hate you for a lifetime.             \\  msmith@cdrom.com
> > 
> > 
> 
> --
>  
>  :{ andyf@speednet.com.au
>   
>         Andy Farkas
>     System Administrator
>    Speednet Communications
>  http://www.speednet.com.au/
>   
> 
> 
> 
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-hackers" in the body of the message
> 

-- 
\\ Give a man a fish, and you feed him for a day. \\  Mike Smith
\\ Tell him he should learn how to fish himself,  \\  msmith@freebsd.org
\\ and he'll hate you for a lifetime.             \\  msmith@cdrom.com




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message