Call-in & call-out on the same line (AGAIN) SOLVED!

[williams at cs.umass.edu]

Thanks to guy at auspex.com, my problem is solved!

In article <7179 at dime.cs.umass.edu>, I write...
"The problem is that if ttyd0 is turned on in /etc/ttytab, a getty is
"sitting on the line and tip complains that all ports are busy even
"though tip is using device cua0 and getty is using ttyd0.
" 
"ps shows:
" 
" 7099 d0 I     0:00 - Fast-Dial-1200 ttyd0 (getty)
" 
"Now, the manual says "You should not see a getty on the port, except
"momentarily as the port receives a call".  This is not true in my
"case, but there are a number of mistakes in this section of the manual
"and another posting on the subject said that the getty running on
"ttyd0 would be "blocked" when cua0 was in use.  Which is correct?
"Should the getty always be there or not?  If I turn line ttyd0 off in
"/etc/ttytab then I can dialout with tip umass.  I have checked for
"lock files in /var/spool and /var/spool/uucp.  For testing purposes, I
"do not now have a modem plugged into the port so there are no
"characters being sent to the port nor is carrier detect being asserted.
" 
It turns out that on the Sun, carrier detect floats high so with no modem
connected the getty unblocks and ties up the line.  When I plugged in the
modem it worked fine.  I had tried it before some time ago with the modem
and it didn't work.  Guess I fixed something else along the way since I
last tried it with the modem.

The correct state is indicated by ps as

  7099 ? I     0:00 - Fast-Dial-1200 ttyd0 (getty)

instead of what I had previously

  7099 d0 I     0:00 - Fast-Dial-1200 ttyd0 (getty)

The question mark in the tty column indicates that the getty isn't actually
on a port yet.  When the modem answers a call, Carrier Detect gets asserted
and the getty gets attached to the line.

Thanks again, Guy!
Leo Pinard c/o williams at cs.umass.edu