larry@tapa.UUCP (Larry Pajakowski) (05/29/88)
I've called SCO tech support who was unable to help so maybe someone out here may have some insight. On our 386 machine at work (configuration below) we have one Trailblazer which we use for dial in/out. Sometimes uucp and cu mark the line as "in use" when the only thing happening is a blocked getty. I've traced this down to ungetty returning a return code of 2 when invoked with no switches on the problem port. This happens both on tty1A as well as some Digiboard ports. Most times disabling and enabling the port restores things though not always. I have to reboot the machine about 2-3 times per week to get things back to normal(?). This causes several calls from users everytime I do it since their DOS LAN software (rightfully) complains about broken connections. The kernal is BIG which may be a factor. It is configured for: Digiboard, Excelan TCP/IP, Xenix-Net, Multiview and VP/ix. The machine is a Compaq 386/20 and Xenix-386 is ver. 2.2.3 (2.2.2 after installing VP/ix). Any help or pointers would be sincerely appreciated. Larry Pajakowski ddsw1!tapa!larry abtcser!larry 1-312-937-1153
john@jetson.UUCP (John Owens) (05/31/88)
In article <582@tapa.UUCP>, larry@tapa.UUCP (Larry Pajakowski) writes: > Most times disabling and enabling the port restores things though not always. > The kernal is BIG which may be a factor. It is configured for: Digiboard, > Excelan TCP/IP, Xenix-Net, Multiview and VP/ix. The machine is a Compaq > 386/20 and Xenix-386 is ver. 2.2.3 (2.2.2 after installing VP/ix). I have the same problem; who shows "DIALOUT" in utmp for the line. You don't need to enable and disable the line; just killing the getty process works every time for me. (init sees that line's process go away and clears the utmp entry, as if someone had logged out of that tty. This is also a "final close", so the tty driver partially resets the line, and drops DTR momentarily.) This has happened for me under 2.2.2 both with and without VP/ix; my kernel isn't nearly that big (standard+tape+Intelliport drivers(+vpix). Good luck! -- John Owens SMART HOUSE Development Venture john@jetson.UUCP (old uucp) uunet!jetson!john +1 301 249 6000 (internet) john%jetson.uucp@uunet.uu.net
jfh@rpp386.UUCP (John F. Haugh II) (06/02/88)
In article <57@jetson.UUCP> john@jetson.UUCP (John Owens) writes: >I have the same problem; who shows "DIALOUT" in utmp for the line. You >don't need to enable and disable the line; just killing the getty >process works every time for me. don't do this if you want you dialouts to work. you will wind up killing off whatever uucico or cu's running on that port. so far as i can tell, if something is on the port killing the getty may kill whatever is using the port going out. you need to check for a lock file before killing anything. i just sent someone else this script. it seems to work just fine so you may want to give it a try yourself. you will have to adjust it for your own situation. - john. -- set - `who -a | grep tty1A` if [ "$1" = "DIALOUT" ] then if [ ! -f /usr/spool/uucp/LCK..tty1A ] then ( who -a | grep tty1A /usr/lib/uucp/ungetty -r /dev/tty1A sleep 5 who -a | grep tty1A ls -l /dev/tty1A echo 'Dialer was hung at ' `date` ) | mail jfh fi > /dev/null 2>&1 fi -- John F. Haugh II | "If you aren't part of the solution, River Parishes Programming | you are part of the precipitate." UUCP: ihnp4!killer!rpp386!jfh | -- long since forgot who DOMAIN: jfh@rpp386.uucp |