On Thu, Nov 04, 1999 at 10:29:53PM -0600, Hanigan Family wrote:
[...]
> > 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!
Check the contents of the lock file. The lock files are suppose
to contain the process id of the process holding the lock. The idea is
that another process attempting to aquire the lock will read the lock
file and then confirm that the process does exist. It should be obvious
that this is non-deterministic, but it's not too bad. It should tell you
who has the lock. If that process doesn't show up in a process display
then you have an app that's not confirming orphaned locks, and I can't
tell you how to proceed then...
Another issue... What is the EXACT error you are getting? I
quite often see initial errors when setting up uucp because the devices
are owned by root and mode 640. Unfortunately, things like cu are suid
to uucp and, consequently can not access the device until I correct the
permissions. The error you get from incorrect permissions is subtly
different from that when you get a locking error. Both will say the
device is busy, but will say it in a different message. With mincom or
kermit, I can't say what the error would be. I tend to use cu because
it is so "stupid" that I know what it's doing and when it's doing it.
Sometimes, simple is better. For me at least.
> Linda
Mike
--
Michael H. Warfield | (770) 985-6132 | [EMAIL PROTECTED]
(The Mad Wizard) | (770) 331-2437 | http://www.wittsend.com/mhw/
NIC whois: MHW9 | An optimist believes we live in the best of all
PGP Key: 0xDF1DD471 | possible worlds. A pessimist is sure of it!
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
