zemon@felix.UUCP (10/31/87)
We have a vax 8600 with a 24 line dmz mux currently running ultrix 2.0. The 24 dmz lines are connected to a Develcon port selector. RS-232 signals available from the port selector are: 2 - Tx 3 - Rx 7 - Gnd 8 - CD 20 - DTR When we originally brought up ultrix 1.2 in this configuration we discovered experimentally that the only way we could get ultrix to 'answer' login requests from the dmz and to do the correct thing in all cases (logout when connection is broken, break connection when user logs out) was to wire together DSR-CTS-CD on the DB-25 connectors at the dmz and run 2, 3, 7, and 20 straight across from the port selector. We of course have appropriate flags set in the system config file, and appropriate entries in /etc/ttys. Things were working fine until we upgraded to 2.0. Everything still works under 2.0, but the errorlog daemon is flooding our error logs with messages of the form: MESSAGE dmzXX: DSR up before DTR Where XX is every number from 00 to 23. There are enough of these messages generated to make the uerf process almost useless for looking at 'real' errors. Since we don't have 2.0 sources yet I can't patch the driver to ignore these spurious errors. I would also like to avoid re-soldering 24 little conectors as this seems to be a software problem in that everything still works. Any suggestions would be appreciated. Tom Arons (arons@iris.ucdavis.edu) Department of Electrical Engineering and Computer Science University of California Davis, CA 95616