> > What I am saying is that after I start mgetty for /dev/ttyS1, I > > cannot access /dev/ttyS1 (like dailing to my isp using chat) anymore > > which is not what the manual of mgetty suggests.
try putting the word "lock" in /etc/ppp/options. also check your /etc/ppp/options and /etc/mgetty/mgetty.config files to make sure you haven't changed the lock file location (should be /var/lock/LCK..`tty`). On Wed, 28 May 1997, Kevin Traas wrote: > This sounds like a device lock contention problem. Try using > /dev/ttyS1 for incoming (i.e. mgetty) and use /dev/cua1 for outgoing > (i.e. PPP). NO! Don't use cua devices for anything. They're obsolete and doing this will CAUSE locking problems if not used carefully. Trying to get cua & ttyS devices working together is a LOT more trouble than using ttyS devices with lockfiles. Use ttyS devices for everything, just make sure that all programs which use it place their lock files in /var/lock. All relevant debian packages already do that (including minicom, pppd, uucp and mgetty). Any programs installed into /usr/local should be compiled to use the same locking method. craig -- craig sanders networking consultant Available for casual or contract temporary autonomous zone system administration tasks. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
