tcamp@numen.UUCP (Ted Campbell) (11/04/88)
Our local dataswitch has been messing up, and this seems to confound my Unix PC. After several tries to connect, it begins giving the message MAX RECOUNT...etc. which evidently is to be translated, "Sir or Madam, I am quite tired of attempting to communicate with the incommunicative computer with which you have requested that I should communicate. Henceforth, therefore, I obstinately refuse to speak, yea, even to dial, said computer." After much searching and no help from the manuals, I have discovered that in /usr/spool/uucp there are files named STST.sys where 'sys' is the name of the system with which you are to communicate. If you become 'su' and eliminate this file, your Unix PC will again at least attempt to communicate. Prior to discovering this, my only recourse was to shutdown and restart. And that, I think, is most objectionable. Wouldn't you agree? -- |Ted A. Campbell |Duke Divinity School | | |Durham, NC 27706 | +--------------------------------+---------------------+ |Email: ...!ecsgate!dukeac!numen!tcamp |
thad@cup.portal.com (Thad P Floryan) (11/06/88)
You really shouldn't have to `su' to delete /usr/spool/uucp/STST.foo The fewer times you `su', the less chance exists for an inadvertent mistake.
erict@flatline.UUCP (j eric townsend) (11/07/88)
In article <106@numen.UUCP>, tcamp@numen.UUCP (Ted Campbell) writes: > > After several tries to connect, it > begins giving the message MAX RECOUNT...etc. which evidently >[...] > If you become 'su' and > eliminate this [STST.systemname] file, your Unix PC will again at least > attempt to communicate. Prior to discovering this, > my only recourse was to shutdown and restart. You don't even have to go to su. Just use this handy little script: ------cut here------ # remst -- deletes status files and does something about MAXCALLS # This first is for non-HDB # rm /usr/spool/uucp/STST* # For HDB: rm /usr/spool/uucp/.Status/* -- "I'm doing a survey on this kind of mindless violence and its affect on the mindless..." -- Max Headroom (who else but?) J. Eric Townsend smail: 511 Parker #2, Houston, Tx, 77007 Inet: COSC3AF@george.uh.edu UUCP: uunet!nuchat!flatline!erict Bitnet: COSC3AF@UHVAX1.BITNET ..!bellcore!tness1!/
kls@ditka.UUCP (Karl Swartz) (11/07/88)
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)