Xref: utzoo unix-pc.general:1634 unix-pc.uucp:70
Path: utzoo!utgpu!watmath!uunet!xanth!nic.MR.NET!hal!cwjcc!tut.cis.ohio-state.edu!mailrus!rutgers!noao!asuvax!nud!mcdchg!ditka!kls
From: kls@ditka.UUCP (Karl Swartz)
Newsgroups: unix-pc.general,unix-pc.uucp
Subject: Re: Eliminating Modem Errors...A Hint
Message-ID: <443@ditka.UUCP>
Date: 7 Nov 88 08:25:41 GMT
References: <106@numen.UUCP> <414@flatline.UUCP>
Reply-To: kls@ditka.UUCP (Karl Swartz)
Organization: Inaction Central, Los Alamos, New Mexico
Lines: 16

In article <414@flatline.UUCP> erict@flatline.UUCP (j eric townsend) writes:
>You don't even have to go to su.  Just use this handy little script:
># remst -- deletes status files and does something about MAXCALLS

Removing *all* status files is rather severe overkill, sort of like
'rm -rf /' because you are running low on disk space.  All you need
is the one for the system that's giving problems.  Also, HDB doesn't
seem to have a MAXCALLS feature.  Instead, it gradually increases
the time before the next retry is made, but never seems to give up
entirely.

-- 
Karl Swartz		|UUCP	{ames!hc!rt1,uunet!dasys1}!ditka!kls
1-505/667-7777 (work)	|ARPA	rt1!ditka!kls@hc.dspo.gov
1-505/672-3113 (home)	|BIX	kswartz
"I never let my schooling get in the way of my education."  (Twain)