uucico is not making the right lock files

[Ross Oliver]

In article <288 at mjbtn.MFEE.TN.US> root at mjbtn.MFEE.TN.US (Mark J. Bailey) writes:
>..................................................... on my client's 2.3
>system (with HDB uucp), when uucico is started and is designated to try and
>make a call on tty1A (Note *A* not 'a'), it creates a lock file for *tty1a*
>even though I have tty1A listed in Devices!  No matter what, it always creates
>a lock file for tty1a instead of tty1A.
....
>My question is, has anyone else experienced this occurance, and if so, (SCO
>are you listening? :-) is this done on purpose and why?  If not, is there
>some way to patch uucico so that it will create the proper lock files.

This was supposed to be a helpful new feature to prevent conflicts
arising from using the modem control and non-modem control devices
at the same time.  uucico (and cu) now translates the last character
of the device name to lower case before creating the lock file.
It should be fairly simple to modify modem-ctl to do this also.
If you can't modify your program, you can get around this feature by
renaming one of the devices so it does not end in a letter, for example,
changing /dev/tty1A to /dev/ttyA1.

If this feature causes too many problems, we may have to un-do it.
However, I think it is an improvement over the previous method, and
modifications to existing programs to account for the change should
be fairly straightforward.  Also, any future programs which access
dialout ports should use the dial(S) library function, which has
been fixed in the 2.3 Development System to work properly with the
current lockfile/dial/getty/ungetty scheme.  That way, any future
changes to the dial/locking scheme can be incorporated into existing
programs by simply linking with the new library.

Ross Oliver
Technical Support
The Santa Cruz Operation, Inc.
uunet!sco!rosso