UUCP on SCO Xenix '386 2.2.2 (bad boy)

[Mark J. Bailey]

I just recently moved up from a Tandy 6000 running MicroSoft Xenix (Tandy
style) version 3.2 to SCO Xenix '386 2.2.2 on a Tandy 4000.  I really
had no trouble to speak of, except for the fact that uucp is acting flakey
when it tries to use a line that is enabled (via UNGETTY) or when some-
thing bombs uucp when the port doesn't disable or the program is interrupted.
I know it sticks DIALOUT in /etc/utmp to make it look like "some one is 
really using the port" to keep other process from grabbing it, but I find
that about at least once or twice a day, uucp either aborts or cannot start
for some reason, and DIALOUT gets left in utmp.  After that, no one can use
it.

My question is, has anybody else experienced these odd behaviors, and if so
what have you done to work around or fix it.  ALso, is UNGETTY really a 
trustworthy program that I can sit back and forget about, I should I try
a bi-directional getty like uutty, or maybe some other alternative.  Why
isn't there a UUGETTY for it already?

I had uucp working like a dream on the 6000 Xenix, but I am very concerned
about SCO uucp.  It even will try and use the port (the dialer) when I am
logged in via a remote terminal and a modem.  I understood from the dialer
code that that isn't supposed to happen either.

Any comments and assistance would be most appreciated.

Thank you.

Mark.

-- 
Mark J. Bailey                                    "Y'all com bak naw, ya hear!"
USMAIL: 511 Memorial Blvd., Murfreesboro, TN 37130 ___________________________
VOICE:  +1 615 893 4450 / +1 615 896 4153          |         JobSoft
UUCP:   ...!{ames,mit-eddie}!killer!mjbtn!root     | Design & Development Co.
FIDO:   Mark Bailey at Net/Node 1:116/12           |  Murfreesboro, TN  USA