[comp.sys.next] HmmMMmmMMmmmmm....

matthews@lewhoosh.umd.edu (Mike Matthews) (05/16/91)

Two questions.  One, has anyone else had problems with using 'talk' to
machines around the Internet?  Specifically, silver.ucs.indiana.edu and my
machine really hate talking to each other quite frequently.  I get errors
such as port already in use, some sort of timeout, 'checking for invitation
on caller's machine,' and so forth.  And sometimes it works.

I tend to think it's not my end, because other stuff has problems with silver
as well.

Second question.  Yesterday, my machine had a near-hang, in that I typed
'netstat' and it just sat there.  After about half a minute things came back
to normal, but my /usr/adm/messages file had an entry of garbage:
May 14 10:25:22 lewhoosh mach: Target 0: NOT READY; retry 3
(the May 14 10: part was a whole bunch of ^@'s until I edited them out in the
hopes that it just choked on the garbage; did it close the file or something
when I emacs'd it?)

It isn't putting *anything* in that file now.  Anybody have a clue as to why?

I feel a reboot coming.....
------
Mike Matthews, matthews@lewhoosh.umd.edu (NeXT)/matthews@umdd (bitnet)
------
"Here's something to think about:  How come you never see a headline like
 `Psychic Wins Lottery.'"
-- Comedian Jay Leno

cnh5730@maraba.tamu.edu (Charles Herrick) (05/16/91)

In article <8587@umd5.umd.edu> matthews@lewhoosh.umd.edu (Mike Matthews) writes:
   has anyone else had problems with using 'talk' to
   machines around the Internet?  

yep. I don't claim that this is true in your case, but my NeXT can't
talk to my professor's SUN SPARC 1+ which is running SUNOS 4.1. The
problem? The version of "talk" in shipping with SUNOS 4.1 is not the
latest version of "talk". Some of the sys-admins at campus have
upgraded the versions of "talk" on their SUNs... by the way, the NeXT
uses the latest version.

   Specifically, silver.ucs.indiana.edu and my
   machine really hate talking to each other quite frequently.  I get errors
   such as port already in use, some sort of timeout, 'checking for invitation
   on caller's machine,' and so forth.  

The check for invitation is normal. 

and later writes..
   I feel a reboot coming.....

Sometimes there's no other way to reset those kernel data structures
in RAM!! go for it! (;-}

--
"Battle not with monsters, lest ye become a monster,
 and if you gaze into the abyss, the abyss gazes also into you."
	-Friedrich Wilhelm Nietzsche