Arun Kahn said:

>Until now, I was under the impression,
>that once a specific device is locked it cannot
>be used by another process (to ensure availablity of
>service by the locking process).  If the **same**
>device can be used by (each using it's locking
>mechanism) mgetty/diald/minicom respectively then
>I am interested in finding out how it can be done.
>I would appreciate if you could share your
>configuration info for the above applications.  It
>would be another selling point for Linux.

It's nothing dramatic.  mgetty only locks the port
when it receives a call.  diald only locks the port
when it makes a call.  minicom locks the port as soon
as it starts until it quits.

So while I have diald and mgetty running all the time,
when minicom starts it locks the port and mgetty and
diald are locked out until minicom is done (makes
sense).

When a call comes in, mgetty locks the port and
diald and minicom are locked out.

When the Internet link (or other link) comes up,
then diald locks the port and mgetty and minicom
are locked out.

Does this all make sense?


____________________________________________________________________
Get free e-mail and a permanent address at http://www.netaddress.com/?N=1

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

Reply via email to