Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!zaphod.mps.ohio-state.edu!magnus.ircc.ohio-state.edu!csn!datran2!smb
From: smb@csn.org!datran2 (Steven M. Boker)
Newsgroups: comp.sys.next
Subject: Re: uucico lock-ups under 2.0 FAQ answer (draft)
Message-ID: <1991Feb25.183151.13248@csn.org!datran2>
Date: 25 Feb 91 18:31:51 GMT
References: <1991Feb25.133608.7343@Axecore.COM> <5357@media-lab.MEDIA.MIT.EDU>
Organization: Data Transforms, Inc.
Lines: 23

In article <5357@media-lab.MEDIA.MIT.EDU> lacsap@plethora.media.mit.edu writes:
>  login prompt.  This is caused by getty hanging.  A simple work around
>  is to have a process run in cron to reset the getty every 15 minutes:
>
>  #! /bin/sh -u
>  PIDS=`ps -ax | bm getty | grep -v bm | awk '{print $1}'`
>  kill -TERM $PIDS

I have found that in order for this script to work reliably, I needed
to add 

kill -HUP 1

to the end of the script.  I have been running this script for 6 weeks
now without a single hung getty state.

Steve.

-- 
 #====#====#====#====#====#====#====#====#====#====#====#====#====#====#====#
 #  Steve Boker           #                 En Vino Kaos                    #
 #  smb@data.com          #                En Kaos Veritas                  #
 #====#====#====#====#====#====#====#====#====#====#====#====#====#====#====#


Brought to you by Super Global Mega Corp .com