Hi, George,

> 
> I have been using diald-0.16.4-1 on a RedHat Linux version 2.0.32 system for
> several
> years without problem.
> 
> I just came back after a day away to find it has been connected to my ISP
> for over 30
> hours ( at local telco rates in the UK !). ( It was running 'normal' and not
> 'forced').

I've run into similar situations.  I put cron scripts to kill diald at night
and restart it in the morning (we have an 8AM to 7PM kind of office...)

Switching to the more recent diald versions (0.99) should get rid of several
wierd and annoying things like that.  (I still kept my cron scripts going,
though...)

If you check on freshmeat.net, there are several "low traffic" programs which
can be used to kill and restart diald when traffic drops to zero on your 
interface, sort of as a backup against this kind of occurence.  (Obviously,
diald should drop the line itself, but if it doesn't...)

Sorry to not have more specific help,

Phil Salkie
Howman Controls
[EMAIL PROTECTED]



-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]

Reply via email to