Moore, Paul wrote: > [snip] > The second problem is the big one - Demon dropped the line on me (for no > reason I could see :-() while my slrnpull session was under way. Diald > proceeded to restart the link, as expected. Great. BUT, when the link > came up again, diald started a SECOND copy of slrnpull (as per the > ip-up.d scripts). This is definitely *not* right :-( This script should be changed to check for an existing running copy first.. > Worst of all, because the link was started by diald, I couldn't stop it > using poff - the process isn't owned by me. I pulled the plug on the > modem as a quick fix... > > I've come to the conclusion that the best way of doing what I'm after is > to dial up manually, using pon. This is no problem. Diald doesn't really > offer me anything extra here, as I basically don't want to dial up on > demand... BUT, once I am online, I'd like to be able to get at the bit > of diald's functionality which monitors the link, and hangs up > (preferably using poff) when the link goes idle for a specified length > of time. Am I missing something? pppd has an 'idle' option that does just that. > Can diald be persuaded to do this (hangup-only, no dialup function)? If > not, how do I get at the ppp link stats to monitor packets going > through? If I can monitor packets/sec across the ppp link, or maybe > traffic over the modem, I could write my own monitor-and-timeout For the most part, pppd can now do most of what people use diald for. The only reason to have both is if you need some of the more advanced control of which kind of packets are considered in the 'idle' determination. Diald does this well. -- This .sig space available for lease. Please contact: Mitch Blevins | mitch_blevins@mindspring.com
Attachment:
pgpxHXLnjRIp1.pgp
Description: PGP signature