[net.micro.att] port not working!!

bwc@ganehd.UUCP (Brantley Coile) (03/05/86)

Does anyone know anything about the serial port on the back of the
AT&T UNIX PC.  We are trying to use it for a terminal port but it will
hang after a random amount of time.  Sometimes it is in one of our programs, 
sometimes it is runnig the getty.  When it you try to 'stty' the port after
it hanges stty hangs.  When you kill stty it reports that it couldn't open
the port.

We are running System V release 1 version 3.0 (the most recent issue).

PLEASE!! If you know anything about it send me mail.

bwc@ganehd.UUCP (Brantley Coile) (03/05/86)

Forgot my signature.


/*
 * Brantley Coile CCP ..!akgua!ganehd!bwc 
 * Northeast Health District/ 468 N. Milledge Ave/ Athens, Ga 30610
 */

smith@ethos.UUCP (03/09/86)

In article <125@ganehd.UUCP> bwc@ganehd.UUCP (Brantley Coile) writes:

>Does anyone know anything about the serial port on the back of the
>AT&T UNIX PC.  We are trying to use it for a terminal port but it will
>hang after a random amount of time.  Sometimes it is in one of our programs, 
>sometimes it is runnig the getty.  When it you try to 'stty' the port after
>it hanges stty hangs.  When you kill stty it reports that it couldn't open
>the port.

I know several UNIX pc owners who have had similar problems,
including myself.  I called the Hotline to report on it, and they
said they "knew about it" and were working on the problem.
Although they have my name, address, and phone number, and
promised to call back, I haven't heard from them.  I can only
assume they haven't fixed it yet.  The AT&T representative hinted
that a complete fix might not be available until the next version
of the software (4.0?).  

The problem occurs less frequently for me now that I installed
the HDB uucp software (with uugetty) that I got from THE STORE!
I am unclear as to exactly what is causing the problem, and
because of that have no clear idea on how to solve it.

jhh@ihlpl.UUCP (Haller) (03/13/86)

I used to have problems with my 7300 port hanging on opens, when I discovered
a generic feature of setting CLOCAL.  I would open /dev/tty000 with
O_NDELAY, then set CLOCAL, and expect to be able to write immediately.
I discovered that CLOCAL has NO EFFECT during the ioctl.  Opening the
/dev/tty000 again, while the fd with CLOCAL set remains open, allows
writes to occur.  If you are trying to write before there is carrier
on the line, this may be the problem.

John Haller