Date: Sat, 15 May 1999 17:58:28 +1000 From: Stanley.Hopcroft@ipaustralia.gov.au To: freebsd-isp@freebsd.org Subject: CANNOT FORK from DeleGate 5.9.1 + FreeBSD 2.2.8-STABLE + P166 + Squid Message-ID: <4A256772.002C0624.00@noteshub01.aipo.gov.au>
next in thread | raw e-mail | index | archive | help
Dear Ladies and Gentlemen, My employer is having trouble with DeleGate 5.9.1 (http://www.delegate.org. Using it with SSLeay to accept SSL) on a FreeBSD 2.2.8-STABLE machine. DeleGate trys to fork a copy of itself to handle each connection but it reports - persistently despite a 10 second sleep before retrying - fork failures. The host is a P166 with 128 MB RAM and 256 MB swap. It runs Apache and Squid 1.1.20. When the problem was occurring, top reported . no more than 30 MB of swap being used and no pageing out . no less than 80% of idle CPU time Also there were no obvious kernel distress calls. Temporarily stopping Squid did pacify DeleGate. Is it normal behaviour for fork to fail on what seems no more than a lightly loaded host? DeleGate runs as "nobody". Shoud I up the limits for nobody in /etc/login.conf ? Your suggestions about delaing with this would be greatfully received. Thank you, Yours sincerely. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4A256772.002C0624.00>