This is Getty-not-block-waiting-on-modem-DCD in view mode; [Up]
Date: Sun 23-Oct-1990 01:13:58 From: goose@surf.sics.bu.oz (Ralph Schwarten) Subject: Getty not block waiting on modem DCD Hi out there ! I am sure that this has been thrashed around before.. unfortunately I didn't pay any attention then :-( My problem is this: I have a 1200 bd modem on ttyb(serial port b not using /dev/ttyb). In /etc/ttys I run getty on that port in the following manner ttydb "/usr/etc/getty d1200" dialup on secure I am using an apple serial cable (it has a printer icon on it) As sson as i kill -1 1 getty forks a login process on ttydb. A ps -ax shows the login process on that port with garbage as it's args. The td and rd light on the modem flash like crazy, stop then start again as soon as the login process dies and getty establishs itself again. Apparently, based on the zs manual entry, ttyd{a,b} is meant to block wait dcd on the modem so that it only forks a login when the modem is actually connected to the remote. Either ttyd{a,b} is not block waiting, or the modem's dcd is always high ? I have tried making a cable from scratch using the pin-outs as specified in the zs man page, although I did not jump 4,8 -->20. The modem works fine if I turn getty of for that port and use tip or cu. So that is my problem.. a frustrating one indeed ! I have not tried a different modem, nor have I tried this modem on the Sun which we have. Although under Microphone II on a mac with the same two cables, we set the software to "wait for call" and everything is sweet. Any hints or solutons to this would be greatly appreciated. Thanks in advance Ralph Schwarten Computing and Information Technology Bond University Gold Coast Queensland Australia e-mail/internet: goose@hal.nmg.bu.oz.au
These are the contents of the former NiCE NeXT User Group NeXTSTEP/OpenStep software archive, currently hosted by Marcel Waldvogel and Netfuture.ch.