Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!zaphod.mps.ohio-state.edu!rpi!uupsi!axecore!lloyd
From: lloyd@Axecore.COM (Lloyd Buchanan)
Newsgroups: comp.sys.next
Subject: Re: uucico lock-ups under 2.0
Keywords: uucp, uucico, support
Message-ID: <1991Feb25.133608.7343@Axecore.COM>
Date: 25 Feb 91 13:36:08 GMT
References: <1481@cgh.UUCP> <434@heaven.woodside.ca.us>
Organization: Axe Core Investors, Inc.
Lines: 32

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
>without wedging the serial port.  If you restrict your UUCP traffic
>to call-only until this bug is fixed, you shouldn't have any problems
>with it locking up.
>
>It's bug #13061.
>
>You should tell your UUCP neighbors not to call you ("Never" in the
>L.sys file) and you should set up your /etc/crontab file to poll
>them every so often.  Send me Email if you don't know how to do this.
>
>Glenn

I have this same extreemly annoying problem.  This worked for me:

	Put a "cp /dev/null /dev/cuf[ab]" in your crontab for 
	execution every 15 min or so.  It seems to clear the hung
	port and doesn't interfere with normal operations.

Lloyd
-- 
Lloyd Buchanan                          lloyd@Axecore.COM
Axe Core Investors                      uupsi!axecore!lloyd
Axe Castle 	                        (914) 333-5226 (phone)
Tarrytown,  NY  10591                   (914) 333-5208 (FAX)


Brought to you by Super Global Mega Corp .com