HDB uucico vs. uugetty

[Rick Richardson]

In article <35 at sopwith.UUCP> snoopy at sopwith.UUCP (Snoopy T. Beagle) writes:
>|I'm running ISC 386/ix, which is SVR3, with HDB uucp.  I have two flavors of
>|COM2 defined:  /dev/tty01, which has no modem control, and /dev/ttyM01,
>|which has modem control.
>
>|If I run uugetty on /dev/ttyM01, uugetty answers the phone OK, but uugetty
>|and uucico trample each other, because uucico creates a lock file called
>|LCK..tty01 while uugetty looks for LCK..ttyM01.  So uucico comes along and

This may not solve your problem, but it worked for me when I had
trouble trying to use the modem device and the direct device at
the same time (I've since hacked in the dialin/out support into
my device driver).

My devices were named:
	com1
	com1m
And I had the same trouble as you do with the lock files.  So I
took advantage of a System V 'feature' - 14 character file names.
I renamed the devices:
	xxxxxcom1
	xxxxxcom1m
Then, when the lock files get created by prepending 'LCK..' to the
device name, both lock files end up with the same name.

The best solution, though, is to apply steady pressure to the UNIX
vendor to incorporate the dialin/out hacks into the device driver.
-- 
Rick Richardson | JetRoff "di"-troff to LaserJet Postprocessor|uunet!pcrat!dry2
PC Research,Inc.| Mail: uunet!pcrat!jetroff; For anon uucp do:|for Dhrystone 2
uunet!pcrat!rick| uucp jetroff!~jetuucp/file_list ~nuucp/.    |submission forms.
jetroff Wk2200-0300,Sa,Su ACU {2400,PEP19200} 12013898963 "" \r ogin: jetuucp