Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!pacbell.com!pacbell!amdahl!netcom!gandrews From: gandrews@netcom.COM (Greg Andrews) Newsgroups: comp.unix.aux Subject: Locked/Unlocked speed issues on T2500 (was Re: A/UX's buggy UUCP) Summary: The modem is used for interactive also. Message-ID: <1991Apr6.060922.10236@netcom.COM> Date: 6 Apr 91 06:09:22 GMT References: <1991Mar28.003019.1764@mauxci.uucp> <1991Apr2.044623.299@intacc.uucp> Organization: Netcom - Online Communication Services UNIX System {408 241-9760 guest} Lines: 48 In article urlichs@smurf.sub.org (Matthias Urlichs) writes: >In comp.unix.aux, article <1991Apr2.044623.299@intacc.uucp>, > mann@intacc.uucp (Jeff Mann) writes: >< 4. Therefore, if you are using a Telebit, you can't use auto baud rate >< adjusting on incoming uucp calls. You must set S50=0 and use the normal >< method of sending breaks to cycle getty until the proper speed is >< attained. >< >??? Why? > >UUCP defaults to using the g protocol. That protocol defaults to requiring >less than 256 unacknowledged bytes; both the modem and the A/UX buffers are >quite capable of storing that many unprocessed characters, therefore there >can't be any soft overruns, therefore no flow control is necessary. > Why? Because the modem can be used for interactive sessions - not just uucp. You're right that uucp doesn't need any flow control because the modem's buffer is large (over 2.5K), and three packets worth of data can be dumped into it without losing anything (assuming the standard packet size of 64 data bytes). Using the Mac's handshake signals for DTR and DCD won't hurt uucp because a lack of flow control won't cause trouble. However, interactive work is a completely different story. If you lock the interface at a high speed and don't have flow control, you run the risk of losing data from buffer overruns. Just dial in at a slower speed like 2400 or 1200 bps, ls a large directory, and watch the bytes fall on the floor. XON/XOFF flow control in the modem can cause trouble for uucp, so that's not a viable option. You can disable XON/XOFF for uucp in a chat script, but that doesn't help with incoming uucp calls. Hardware handshaking would take away the ability for the Mac to detect a disconnected session, causing security problems. About the only thing left is to unlock the modem's speed so interactive callers don't need to have overrun trouble and the system can detect an unexpected hangup. -- .------------------------------------------------------------------------. | Greg Andrews | UUCP: {apple,amdahl,claris}!netcom!gandrews | | | Internet: gandrews@netcom.COM | `------------------------------------------------------------------------'