From: bryan@uhura1.uucp (A. Bryan Curnutt) Subject: Re: Modem problems (inittab/getty/uugetty) ... Date: Sun, 30 May 1993 17:51:30 GMT
In article <JIIVEE.93May30022526@lk-hp-3.hut.fi> jiivee@hut.fi writes:
>
> For more information consult init(8) manual page.
This would be easier if there _were_ an init(8) man page in SLS...
>Getty/uugetty doesn't wait for connection properly. By default,
>if init starts one process 10 times during 2 minutes period, it
>thinks that there is something weird or wrong in configuration
>and refuses to start that process for 5 minutes.
And, in my experience, this is the correct behavior.
>:> c6:6:respawn:/bin/uugetty 19200,14400,9600,4800,2400,1200,300 ttys1
>
>You don't have to list all those baudrate and other options on
>command line rather you can set them up on your gettydefs file.
And indeed, you need to set them up in /etc/gettydefs. At least the
man page for getty doesn't say anything about being able to accept
a speed entry of "19200,14400,9600,..."
># /etc/inittab
># [...]
># set /dev/ttyS1 and /dev/cua1 to 8-bit clean mode and use RTS/CTS
># flow-control (modem)
>#
>m1::bootwait:/bin/stty sane pass8 -clocal crtscts < /dev/ttyS1
>c1::bootwait:/bin/stty sane pass8 -clocal crtscts < /dev/cua1
Are these lines actually useful in any way? The stty done at boot
time should be overridden by whatever getty/uugetty does. You can
set the line parameters in the gettydefs entry, like so:
19200# B19200 CS8 -CLOCAL CRTSCTS # B19200 SANE -ISTRIP -CLOCAL CRTSCTS #\
@S login: #19200
The -CLOCAL shouldn't even be necessary -- at least nothing appears
to set clocal on my system.
-- Bryan Curnutt Stoner Associates, Inc. bryan%uhura1@uunet.uu.net (713)626-9568 voice (713)622-7832 fax