I have looked thoroughly through the archives for an answer to this, but
have found no answer.
The solution I suppose would be to make MAJOR timeouts in
redial-backoff-start rediald-backoff-limit and dial-fail-limit But I think
that would be far too messy for something that I think should be SIMPLE to do.
I have mgetty setup on the same device (Yes I read the FAQ) as diald.
Mgetty answers the call no problem...diald doesn't seem to notice/care
about it. However As soon as a non-local request comes from the dialin
session (or anywhere local), off goes diald to try and use that device. Of
course it can't because mgetty is using it.
After diald goes through all the retrys I set it up to do, it simply stops
responding. Even after the dialin session closes.
The diald-examples explains this to be normal, and says diald will now sit
and wait for an operator to issue a command to restart.
Would it be that hard to add in a command that will reset diald after the
last try failed, back to idle/waiting mode for situations such as this?
I'm no programmer, but it seems like it shouldn't be too hard to add in.
PLEASE consider it.
If there is someway of doing this that I haven't yet found, please do tell.
Mgetty is quite nice about all of this. When diald takes the line from it
it spits out one complaint then sits there quietly waiting for the line to
be available.
Any ideas or suggestions would be appreciated.
Dan
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
