10 messages in org.freebsd.freebsd-ispRe: Logging pppd connect & disconnect| From | Sent On | Attachments |
|---|---|---|
| Steve Reid | May 15, 1996 4:13 pm | |
| Nate Williams | May 15, 1996 9:20 pm | |
| Steve Reid | May 15, 1996 9:53 pm | |
| Nate Williams | May 15, 1996 10:18 pm | |
| Neal Rigney | May 16, 1996 7:29 am | |
| Rob Simons | May 16, 1996 8:45 am | |
| Steve Reid | May 16, 1996 1:57 pm | |
| Neal Rigney | May 16, 1996 8:17 pm | |
| Daniel O'Callaghan | May 16, 1996 8:40 pm | |
| Nate Williams | May 16, 1996 9:14 pm |
| Subject: | Re: Logging pppd connect & disconnect | |
|---|---|---|
| From: | Nate Williams (na...@sri.MT.net) | |
| Date: | May 16, 1996 9:14:48 pm | |
| List: | org.freebsd.freebsd-isp | |
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