>1. Diald appears to leave the tty port in a state that doesn't allow
>any other programs to access it after diald exits.
Curious. It was a couple of diald revs ago, but I used to run a machine
where diald coexisted quite happily with mgetty - once diald finished a
dialout, mgetty would start monitoring the port again.
It's just occurred to me that during setting this up, I did find a problem
similar to what you describe. You're not using a soft link in /dev are you?
E.g. /dev/modem -> /dev/ttyS1? If you are, try replacing it with a hard
link - ownership stuff doesn't get changed properly on a soft link.
--
Jim Hague - [EMAIL PROTECTED](Work),[EMAIL PROTECTED](Play)
Canon Information Systems Research Australia +61 2 9805 2854
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
