From owner-freebsd-net@FreeBSD.ORG Mon May 19 22:08:45 2008 Return-Path: Delivered-To: net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3C2CE106568C for ; Mon, 19 May 2008 22:08:45 +0000 (UTC) (envelope-from einstein@yawl.com.br) Received: from server13.yawl.com.br (server13.yawl.com.br [200.175.230.13]) by mx1.freebsd.org (Postfix) with ESMTP id 8E4E78FC1C for ; Mon, 19 May 2008 22:08:44 +0000 (UTC) (envelope-from einstein@yawl.com.br) Received: from [127.0.0.1] ([200.175.230.100]) by server13.yawl.com.br (IceWarp 9.2.1) with ASMTP id ZBB64041; Mon, 19 May 2008 19:08:41 -0300 Message-ID: <4831FA6A.1080906@yawl.com.br> Date: Mon, 19 May 2008 19:08:42 -0300 From: Einstein Oliveira User-Agent: Thunderbird 2.0.0.14 (Windows/20080421) MIME-Version: 1.0 To: Julian Elischer , FreeBSD Net Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Antivirus: avast! (VPS 080519-0, 19/05/2008), Outbound message X-Antivirus-Status: Clean Cc: Subject: Re: Suggestions on a PPPoE server with mpd X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 May 2008 22:08:45 -0000 > Einstein Oliveira wrote: >> Julian Elischer wrote: >>> Einstein Oliveira wrote: >>>> Hi all, >>>> >>>> In an attempt to change from pppoed + ppp to mpd I'm having some >>>> strange behaviour with the later on the same host that usually >>>> handles 100+ clients with the former. >>>> >>>> Basically it's a i386 FreeBSD 6.3 system with mpd-5.1 and 1 GB Ram. >>>> Users can connect without any problem. >>>> >>>> After a few minutes a SECOND mpd process is initiated and this one >>>> consumes all idle processing of the host. >>>> >>>> Whoever is connected before that still remains connected but no new >>>> user can get in anymore. Also logging stops being generated. >>>> >>>> The only solution is a killall -KILL on mpd. >>>> >>>> On another host I have the same configuration working as expected but >>>> with less than 50 clients. >>>> >>>> Both configurations are the same from mpd.conf.sample. >>>> >>>> So I'm looking for any suggestions that somebody has been using to >>>> handle that many pppoe connections (100+) with mpd. >>>> >>>> >>>> >>>> Thanks, >>>> >>> >>> >>> people have handled many more than 100 I think.. >>> however there is no reason that a 2nd should start up. >>> what is teh PPID of the 2nd? >>> >>> are you sure that it isn't being started up by whatever starts up the >>> first? >>> >>> >> >> The second process has a bigger PID than the first and I'm using the >> default /usr/local/etc/rc.d/mpd5 as startup script with mpd_enable="YES" >> on /etc/rc.conf. > > what about the PPID? (Parent PID) ps alx shows this. > >> here is the output of ps -alx: 0 12573 1 0 20 0 5424 3468 kserel Ss ?? 0:00.15 /usr/local/sbin/mpd5 -p /va 0 12629 12573 283 131 0 5424 3452 - R ?? 0:36.94 /usr/local/sbin/mpd5 -p /va 0 12707 11713 0 96 0 1528 868 - R+ p0 0:00.00 grep mpd5 -- Einstein Oliveira einstein@yawl.com.br ___________________________________________________ Yawl Internet Ltda. http://www.yawl.com.br/