Date: Tue, 14 Dec 1999 12:28:22 +0100 (CET) From: Arjan van der Oest <arjan@nl.demon.net> To: freebsd-isp@freebsd.org Subject: 3.3r & Radius Message-ID: <Pine.BSF.4.10.9912141222160.1443-100000@bunker.noc.nl.demon.net>
next in thread | raw e-mail | index | archive | help
Hi all, We're running a couple of 3.3r boxes doing Radius auth. We use our own and very modified source for Radius. This has been working quite well running under 2.2.7 and 3.1. Recently we'ce changed over to 3.3r and that's when the shit hit the fan : Radius is only allowed to spawn 100 child processes. We've seen it happen twice now that Radius *thinks* it has more then 100 childs running and refuses any more connections while there are actually *none* except for the father. Somehow Radius is not receiving the sig child signal and is waiting for one or more childs to die. Well, this might be a bug in our Radius source code (and we're looking in to that) but what puzzles me is that it always worked under 2.2.7 and 3.1. Question : is anyone aware of any changes in the way sig child signals are issued or handled under 3.3-r or possible someone has the same problems. Let me know, last night all of our radius boxes died allmost at the same time, leaving my NOC without any customer authentification :( This happened twice now in one week and I'm NOT a happy bunny... ao -- arjan van der oest - systems administrator - arjan@nl.demon.net Demon Internet NOC, Amsterdam. www.demon.nl My views cannot be held to represent those of Demon Internet... "Gewoon door mijn droom te onthouden..." 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?Pine.BSF.4.10.9912141222160.1443-100000>