From owner-freebsd-isp Thu May 16 21:15:55 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id VAA08438 for isp-outgoing; Thu, 16 May 1996 21:15:55 -0700 (PDT) Received: from rocky.sri.MT.net (rocky.sri.MT.net [204.182.243.10]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id VAA08423 for ; Thu, 16 May 1996 21:15:51 -0700 (PDT) Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id WAA25718; Thu, 16 May 1996 22:15:08 -0600 Date: Thu, 16 May 1996 22:15:08 -0600 From: Nate Williams Message-Id: <199605170415.WAA25718@rocky.sri.MT.net> To: "Daniel O'Callaghan" Cc: Nate Williams , Steve Reid , isp@freebsd.org Subject: Re: Logging pppd connect & disconnect In-Reply-To: References: <199605160420.WAA21638@rocky.sri.MT.net> Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > > Is there any way to log when users connect and disconnect with pppd? > > > > Sure, it's a piece of cake. How do your users startup PPP? On my box > > they run a little shell script which is customized for each system, so > > it would be trivial to have it append start/stop entries to a file. > > What about a generic solution? The problem with the Nate's suggestion is > that one ends up with a sh process for every pppd, while someone is > logged in. This is a non-issue on FreeBSD. Because the sh process is nevery used, it will get swapped out until it's used again. So, you take the hit of a few K in your swap file (maybe not even that) for every PPP process. Doing it this way is a very *generic* solution. > I exec pppd, on my own ISP TS, but that prevents the logout > message from being run. I do too, but I modified the script I sent out for that very reason. Exec'ing pppd is also a better solution security wise as well, since it doesn't allow the user to *ever* do anything once PPP is running. Nate