Bug#5014: diald won't do what I want
firstname.lastname@example.org wrote on 30.10.96 in <email@example.com>:
> I am still unable to do what I want to do. Fundamentally,
> this is a bug in the current implementation of "impulse".
> What I want is diald to:
> (a) bring up the line if it's needed
> (b) guarantee that the line will be brought back up if there's
> been recent activity, and
> (c) leave the line up until external factors take it down.
> In other words, I "never" want diald to hang up the phone.
And why do you think that "impulse" has anything to do with that? As I
understand it, "impulse" is meant for people (like me) who have to pay by
the minute (or some other time quantity), where you want to take down the
line - as long as it is idle - just before your time quantum runs out.
Doesn't sound similar to your situation.
Anyway, "impulse" seems to work just fine for me. And from your
description, I don't quite understand what goes wrong for you.
You said something about the line going active "by itself". Are you
*certain* it's not because, say, a demon tries to contact a DNS server?
You might try to run tcpdump to see what packets are forcing the
connection back up. Or was it some other problem?
> (Actually, it's fine for diald to hang up the phone if it's not used
> for an extremely long period of time -- say, after a whole day of
> inactivity. However, it's important to me that there be a
> significant period of time where if the phone is hung up, diald
> won't redial. From reading the documentation, the "impulse"
> option should do exactly what I want.)
>From what I (believe to) understand, "impulse" has nothing to do with