I run this all the time, for the same reason as was previously listed - I
have one dialup to work and one to my ISP.
Often I will use the house line for one (work) and the other line for my
ISP, but I routinely switch the modems around.
Here is my normal configuration:
(External) Modem 1: House Line
Running: diald (to work)
(External) Modem 2: Data Line
Running: diald (to ISP)
mgetty (to answer phone - data and fax)
Minicom is also occasionally run if need be. Since I use the /dev/ttyS*
devices through-out, all of the programs will lock the serial port
appropriately when they need it.
Running two different dialds, you have to set up two different
configuration files, and move all of the appropriate files to separate
files - this includes log files, pid files, the FIFO pipe, and several
files.
Then, when I want to switch the work diald over to the data line - which
I did frantically the other night when I discovered someone was on the
voice line AFTER I told it to dial out! - to switch it over I just change
the device line to the other modem (after quieting down the dialout and
all) and pipe a "RESET" into the FIFO pipe.
I might add I wrote a script to react to one or more commands and then to
send the commands to the FIFO pipe. For example, you might say "work
debug 4" or "work up" and it would look for a FIFO pipe in a directory
called "/etc/diald/work" with the name "diald.ctl" and send the commands
to it.
I'm planning on releasing my dual diald setup to all of you sooner or
later - does such a thing have a demand? Also, it would be in an RPM -
everyone should use these things :-)
David Douthitt
[EMAIL PROTECTED] -or- [EMAIL PROTECTED]
"It's not over till the fat guy in the plaid shirt gets
thrown out by the ushers." - Harold, "The Red Green Show"
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
