Path: utzoo!news-server.csri.toronto.edu!rutgers!uwm.edu!spool.mu.edu!uunet!wuarchive!udel!haven!umd5!lewhoosh.umd.edu!matthews
From: matthews@lewhoosh.umd.edu (Mike Matthews)
Newsgroups: comp.sys.next
Subject: Monitor (was Re: Kermit and *lots* of system CPU time - why?)
Message-ID: <8163@umd5.umd.edu>
Date: 5 Mar 91 15:00:32 GMT
References: <4MAR91192237@uazhe0.physics.arizona.edu>
Sender: news@umd5.umd.edu
Distribution: usa,local
Organization: Computer Science Center, University of Maryland, College Park
Lines: 22

In article <4MAR91192237@uazhe0.physics.arizona.edu> zazula@uazhe0.physics.arizona.edu writes:
>I'm also running the Monitor program that was mentioned on this list.

Just out of curiousity, has anyone else had problems with Monitor?  I did all
the fixes as that article said, but every time I ran it, weird things happened.
Weird things as in oh-boy-I-get-to-reboot-again.

Friend of mine copied my binary to his NeXTstation (I have a NeXTstation too,
for the record), and it just dumped core.  His machine wasn't on the net and
I had it configured to look at the Ethernet, so that may have caused that,
but still..

>Thanks,
>Ralph

------
Mike Matthews, matthews@lewhoosh.umd.edu (NeXT)/matthews@umdd (bitnet)
------
Langsam's Laws:
	1) Everything depends.
	2) Nothing is always.
	3) Everything is sometimes.