From owner-freebsd-security Tue May 18 15:33:23 1999 Delivered-To: freebsd-security@freebsd.org Received: from aniwa.sky (p22-max8.wlg.ihug.co.nz [209.79.142.214]) by hub.freebsd.org (Postfix) with ESMTP id A893714DDA for ; Tue, 18 May 1999 15:33:14 -0700 (PDT) (envelope-from andrew@squiz.co.nz) Received: from aniwa.sky (localhost [127.0.0.1]) by aniwa.sky (8.9.1a/8.9.1) with ESMTP id BAA09186; Wed, 19 May 1999 01:56:28 +1200 (NZST) Message-Id: <199905181356.BAA09186@aniwa.sky> X-Mailer: exmh version 2.0.2 2/24/98 To: junkmale@xtra.co.nz Cc: freebsd-security@FreeBSD.ORG Subject: Re: http attack(?) In-reply-to: Your message of "Tue, 18 May 1999 21:49:49 +1200." <19990518095202.EPCY7623210.mta2-rme@wocker> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 19 May 1999 01:56:28 +1200 From: Andrew McNaughton Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > A few days ago, I noticed my machine was running extremely slowly. I did a top 10 at the console and > got "too many open files". Existing telnet sessions were non-responsive. New telnets would not start. > > I then tried a top 5. named and syslogd were busy. > > I looked at httpd.error and 21 of these spread over 14 seconds: > [Sat May 15 16:45:34 1999] accept: (client socket): Too many open files in system I'm not too sure whether to trust that the restriction on file handles is system wide. Some programs may not know about FreeBSD's process limits scheme. Check the output of 'limits' and 'sysctl -a | grep maxfiles'. They might give you a better idea what is happening. The context in which you run limits is important, but if your shell is failing, then that shell is probably a good thing to have a look at. limits is a shell built-in under sh and bash, and will not spawn a new process. Andrew McNaughton -- ----------- Andrew McNaughton andrew@squiz.co.nz http://www.newsroom.co.nz/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message