snip
> 1) You can change "respawn" to "off" in /etc/inittab and then
>execute "/sbin/init q" to turn off an "mgetty". This is not Windows.
>You do not have to reboot! (Anyone want to write and "enable"/"disable"
>pair that does this automagically? I use to do this on SCO a lot. Maybe
>an equiv already exists and I just don't know what it is...)
>
Thanks I knew there had to be a better way
> 2) If your software is configured correctly, both mgetty and
>cu and minicom and kermit and and uucp and whatever should all agree
>on where the lock files are. When something comes up, it checks for
>a lock file (someone logged in). If the lock file doesn't exist, it
>creates one and accesses the drive. As soon as mgetty senses data, it
>checks for someone else having a lock file. If it finds a lock file,
>it goes to sleep waiting for whoever to finish. When they finish, mgetty
>reinitializes the modem and waits on it. When mgetty detects someone
>dialing in, it creates a lock file to lock out the dial-out utilities
>while Joe Shmuck is playing on the tty. The lock files are the key.
>They allow all of these guys to play nicey nicey. But they all have to
>agree on the lock files.
>
But the problem is the lock file exist I guess I need to check out all the
config
files maybe I have it setup to prevent calling out since I went and checked
my other machine that is running mgetty and you are right no lock file. I
would
have sworn they were set up the exact same way and they are running the same
group of programs, mgetty, minicom and kermit. Why one should take notes
when
they are setting things up!
Linda
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
