Date: Thu, 16 May 1996 09:29:34 -0500 (CDT) From: Neal Rigney <neal@mail.pernet.net> To: Steve Reid <root@edmweb.com> Cc: Nate Williams <nate@sri.MT.net>, isp@FreeBSD.org Subject: Re: Logging pppd connect & disconnect Message-ID: <Pine.NEB.3.93.960516092537.10686A-100000@jennifer.pernet.net> In-Reply-To: <Pine.BSF.3.91.960515213518.655B-100000@bitbucket.edmweb.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 15 May 1996, Steve Reid wrote: > It's done with a line in /etc/ttys: > > ttyd1 "/usr/sbin/pppd -detach 115200" unknown on secure > > This makes the winsock scripts extremely simple, but it doesn't leave > much opertunity for customized logging. > Out of curiosity, does Win95 work for you without scripting? Anyway, try using ip-up and ip-down for logging. Our machines aer set up to syslog to a master log machine. The ip-up script just does a "logger" command to log the info we want. ip-up gets passed ip address, ppp interface, etc. It also makes debugging a connection better, since it doesn't execute ip-up until after the interface is ready to send/receive packets. Also, I think the newest pppd (in -stable) logs the amount of time pppd was used to syslog. That may do close enough to what you want without any hassle. -- Neal Rigney, PERnet Communications, (409)729-4638 neal@mail.pernet.net My opinions are mine, damnit! PERnet can't have them!
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.NEB.3.93.960516092537.10686A-100000>