Hi Alan, I agree with you on the performance side of it - you'd never even consider running apache out of inetd - I don't have the levels of traffic to worry about the [Linux] default 40 spawned processes / 60 seconds. I'm still not sure about what's causing my problem (I'm fairly sure its something to do with client disconnects - two sets of people both have problems in different distinct offices and their internet access is not the norm - one office is on experimental high speed DSL (lots of mega bits) and the other office is on a wireless link so maybe its something related to their networks - or else its something to do with their MS Outlook clients).
Derek -----Original Message----- From: Alan Brown [mailto:[EMAIL PROTECTED] Sent: 16 February 2004 20:18 To: Chris Payne Cc: Derek Conniffe; [EMAIL PROTECTED] Subject: RE: POPPER jamming On Mon, 16 Feb 2004, Chris Payne wrote: > I've increased the nowait from its default(100 I believe) to > nowait.400 This detects whether the pop client has disconnected or is > failing to respond. More-so for if you have dial-up users or users > with Outlook. Uh, no. Nowait.XXX changes inetd's default shutdown parameters (40 calls in 60 seconds) to whatever XXX is before deciding the process is looping. In your case: 400 calls per minute. It would be better to make qpopper persistant and switch from nowait.400 to wait. The forkload will be significantly less for starters. --- Incoming mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.583 / Virus Database: 369 - Release Date: 10/02/2004 --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.583 / Virus Database: 369 - Release Date: 10/02/2004
