Thx for the tips guys. I sort of figured out that inetd was not spawning fast enough, but just didn't know where to tweak it. I appreciate the help Brian, Mikkel. :) Rgrds, Wong. > -----Original Message----- > From: owner-linux-net@vger.rutgers.edu > [mailto:owner-linux-net@vger.rutgers.edu]On Behalf Of Brian > Sent: Thursday, July 20, 2000 12:06 PM > To: C.M. Wong; linux-net@vger.rutgers.edu > Subject: Re: pop 3 error > > > On Wed, 19 Jul 2000, C.M. Wong wrote: > > Hi All, > > > > Lately, I have been encountering some prob with my pop service. > I get the > > below error on /var/log/message: > > > > inetd[18313]: pop-3/tcp server failing (looping or being flooded), s > > ervice terminated for 10 min > > The error says it all: it's spawning processes faster than the threshhold > allows and closes service for 10 minutes (and yes, it will come > back if you let > it sit there for awhile). > > >From the man page ("man 5 inetd.conf"): > The optional ``max'' suffix (separated from ``wait'' or > ``nowait'' by a dot) > specifies the maximum number of server instances that may be spawned from > inetd within an interval of 60 seconds. When omitted, ``max'' > defaults to 40. > > The 40 connections/minute acts as an emergency brake to limit the damage a > DoS'd service can do. However, if you run a busy mail server, it > is possible to > exceed 40 connections/minute of legitimate traffic. If you see > this warning > in normal operation, up the limit. In inetd.conf, look for this line: > pop-3 stream tcp nowait root > > change nowait to nowait.## such as: > pop-3 stream tcp nowait.80 root > > -- Brian > - > : send the line "unsubscribe linux-net" in > the body of a message to majordomo@vger.rutgers.edu - : send the line "unsubscribe linux-net" in the body of a message to majordomo@vger.rutgers.edu
