From owner-freebsd-questions Tue Jan 23 19:40: 7 2001 Delivered-To: freebsd-questions@freebsd.org Received: from femail10.sdc1.sfba.home.com (femail10.sdc1.sfba.home.com [24.0.95.106]) by hub.freebsd.org (Postfix) with ESMTP id 98E6737B401 for ; Tue, 23 Jan 2001 19:39:46 -0800 (PST) Received: from [192.0.0.27] ([24.7.223.67]) by femail10.sdc1.sfba.home.com (InterMail vM.4.01.03.00 201-229-121) with ESMTP id <20010124033933.HMUN6975.femail10.sdc1.sfba.home.com@[192.0.0.27]> for ; Tue, 23 Jan 2001 19:39:33 -0800 Mime-Version: 1.0 X-Sender: ralph99@mail.voicenet.com (Unverified) Message-Id: In-Reply-To: References: Date: Tue, 23 Jan 2001 22:39:27 -0500 To: freebsd-questions@freebsd.org From: Ralph Dratman Subject: inetd services very slow to respond Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Any and all, I'm a new (several months old) user of FreeBSD 2.2. Using the really excellent Lehey book I have managed to set up an FTP/web/mail/DNS server on an old Pentium 100 with 103 MB RAM, which has been working quite nicely. I am quite impressed and in general have absolutely no complaints. Tons better and more organized than Linux, seems to me. Last week, however, the computer experienced a power failure. Since then - and of course I can't really prove the correlation - the services which need to be run by inetd have been starting up VERY slowly, with delays of more than a minute before anything happens. The services where I've observed the problem are FTP, telnet, and pop3. Once a service starts up, it operates without any problem and apparently at full speed. If I use the service again within a minute or two, there is little or no delay. If I wait longer, there is some delay. The full delay appears after I've left the system alone for a longer time. At first I thought maybe the hard drive was spinning down or something, maybe a flipped controller option bit, but apache always responds without any delay, as does console login, so that theory seems untenable unless I'm being badly misled by data already in RAM, which I doubt. I've learned my lesson and have a UPS on order, but I still have to fix the system. I tried killing inetd and restarting it, both with and without the -wW flags, but that didn't make any difference. Here's a nice little mystery... we all love a mystery... don't we? Thanks in advance for any thoughts or insights. Regards, Ralph Dratman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message