Date: Thu, 16 May 1996 22:15:08 -0600 From: Nate Williams <nate@sri.MT.net> To: "Daniel O'Callaghan" <danny@lynx.its.unimelb.edu.au> Cc: Nate Williams <nate@sri.MT.net>, Steve Reid <root@edmweb.com>, isp@freebsd.org Subject: Re: Logging pppd connect & disconnect Message-ID: <199605170415.WAA25718@rocky.sri.MT.net> In-Reply-To: <Pine.BSI.3.91.960517133352.7039D-100000@lynx.its.unimelb.edu.au> References: <199605160420.WAA21638@rocky.sri.MT.net> <Pine.BSI.3.91.960517133352.7039D-100000@lynx.its.unimelb.edu.au>
next in thread | previous in thread | raw e-mail | index | archive | help
> > > 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199605170415.WAA25718>