ECU BUG LIST as of
Thu Mar 31 13:27:42 EST 1994

This 3.30 release was languishing, with little time for
work, so I have released it with these known bugs
(as well as the usual litnany of UNknown bugs :>).

1.  Sometimes on the initial setup screen, if you attempt to open
a non-existent tty, correct the error, then retry the open, ECU
will terminate.

2.  When on SCO or other ECU platform using ecuungetty, you have
to be careful of a possible race condition when switching lines
(closing one, open another).  If you close one tty "name" and
immediately open a different tty "name" which refers to the same
physical device, ECU may abort with "line owned by uucp." For
instance, you may have /dev/tty2a open and "Home dial" a
directory entry which specifies /deb/tty2B.

This is a bug in an otherwise useful piece of logic that provides
ECU with better shared modem support than (most) other similar
programs.  What is happening is:

  a. ECU releases the old line, telling ecuungetty to cycle the getty.
  b. ecuungetty chowns the line to uucp and kills getty
  c. getty locks the tty and begins its initialization of the line
     for dial-in
  d. meanwhile, ECU is trying to open the same line by another name
     and runs into the ownership problem.

ECU "thinks" he knows what is going on, so it treats the
unexpected uucp ownership as a sort of logic error.  This problem
could be solved if ECU knew the relationship between tty names.
models/tty.equiv is a start, but I had no time.

Workaround: consistently use one tty name for each physical device.
