Path: utzoo!dciem!nrcaer!scs!spl1!laidbak!att!osu-cis!killer!vector!rpp386!jfh From: jfh@rpp386.UUCP (John F. Haugh II) Newsgroups: comp.unix.xenix Subject: Re: ungetty woes Message-ID: <2283@rpp386.UUCP> Date: 1 Jun 88 18:24:46 GMT Article-I.D.: rpp386.2283 References: <582@tapa.UUCP> <57@jetson.UUCP> Reply-To: jfh@rpp386.UUCP (The Beach Bum) Organization: Big "D" Home for Wayward Hackers Lines: 37 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 |