lacsap@plethora.media.mit.edu (Pascal Chesnais) (02/26/91)
In article <1991Feb25.133608.7343@Axecore.COM> lloyd@Axecore.COM (Lloyd Buchanan) writes: > In article <434@heaven.woodside.ca.us> glenn@heaven.woodside.ca.us (Glenn Reid) writes: > >In article <1481@cgh.UUCP> paul@cgh.uucp (Paul Homchick) writes: > >>I am having an intermittent problem with uucico lock-ups. Three times > >>since installing version 2.0 of Nextstep, I have had uucico lock up > >>the serial port. > > > >There is a serious bug in the serial driver in 2.0 related to > >incoming calls (and uucico). You basically can't receive calls > >It's bug #13061. > Put a "cp /dev/null /dev/cuf[ab]" in your crontab for Below is the entry for the FAQ on the subject, note that it is a draft so it still needs to be cleaned up. The cron solution of finding getty is a recommended on. pasc 37. Under 2.0 running UUCP and other dialins conditions hangs the dialup line, what can I do? (draft) There is a bug in the serial driver which causes getty to get stuck. The situation arises after a successful uucico connection, subsequent connections via modem will get a connection with the modem, but no 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 Of course trying to connect when the script is running will not allow you to connect, try again a minute later. This fix will not affect on-going UUCP or interactive connections. This will probably be fix in the next kernel release. Pascal Chesnais, Research Specialist, Electronic Publishing Group Media Laboratory, E15-351, 20 Ames Street, Cambridge, Ma, 02139 (617) 253-0311 email: lacsap@plethora.media.mit.edu (NeXT)
datran2 (Steven M. Boker) (02/26/91)
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 # #====#====#====#====#====#====#====#====#====#====#====#====#====#====#====#