Date: Fri, 29 Nov 1996 11:13:54 +1100 (EST) From: "Daniel O'Callaghan" <danny@panda.hilink.com.au> To: Travis Mikalson <tmikalson@obiwan.terranova.net> Cc: isp@freebsd.org Subject: Re: Idle Timeout Message-ID: <Pine.BSF.3.91.961129105612.1605R-100000@panda.hilink.com.au> In-Reply-To: <329E1F58.7191@terranova.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 28 Nov 1996, Travis Mikalson wrote: > Daniel O'Callaghan wrote: > > Are you running shell accounts, iijppp or pppd? > pppd 2.2.0 > > > iijppp has its own idle timeout code. tcsh has idle timeout code. I've > > written a program which does idle timeout on pppds but I have not yet got > > it to start up automatically. (Too many other things to do.) You can > Something wrong with cron? OK, you can get it from ftp.hilink.com.au:/pub/Net/watchifpkts.tgz Syntax is: watchifpkts ppp0 20 5 12345 which means watch ppp0; idle is a 20 minute block with less than 5 packets per minute each minute. HUP process 12345 if idle. BUGS: the watcher uses sleep(60). If it finds the if is down, it exits, but it is possible for a user to log out, and another to log in on the same interface in that 60 second period. The original watcher will not notice, and will have the wrong pid. The best way to start it would be for pppd to fork and exec, after it has decided on its ppp interface number. pppd should also send the watcher a TERM when it is exiting, to avoid the problem in the above paragraph. Best of all would be for this to be integrated into pppd itself. Danny
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.91.961129105612.1605R-100000>