gast@lanai.cs.ucla.edu (03/11/89)
What is with this program? It sends out too many messages. It is
impossible to get any work done in the 5 or 10 minutes before a
machine goes down because every terminal is messed up by these
messages.
This problem is particularly annoying if one is running X windows,
then the messages come to all the windows and not just one. Each
window has to be fixed.
I fail to see why we must get so many messages. In particular, I
object to receiving two or three messages in the span of a minute,
telling me something like ``unused_host going down in 3 minutes.''
Our sys admins say they can do nothing about this problem because
of the way Sun wrote the program. Is this really true? Isn't
there some undocumented option they can specify that will be less
verbose?
Thanks for your consideration.
David Gast
gast@cs.ucla.edu
{uunet,ucbvax,rutgers}!{ucla-cs,cs.ucla.edu}!gastyoram@garfield (Yoram Eisenstadter) (03/14/89)
In article <21613@shemp.CS.UCLA.EDU> gast@CS.UCLA.EDU () writes: >What is with this program? It sends out too many messages. It is >impossible to get any work done in the 5 or 10 minutes before a >machine goes down... >... >Our sys admins say they can do nothing about this problem because >of the way Sun wrote the program. Is this really true? Isn't >there some undocumented option they can specify that will be less >verbose? > >David Gast >gast@cs.ucla.edu >{uunet,ucbvax,rutgers}!{ucla-cs,cs.ucla.edu}!gast I also used to be plagued by numerous messages about hosts all over our network being shut down. These messages actually come to you courtesy of an RPC program called "rwall" (remote "wall"), which "shutdown" calls to send messages to remote hosts which it thinks might be interested. One easy way to avoid getting any such messages is to disable the rwall daemon that runs on your workstation (rwalld). You can do this by commenting out its entry in your /etc/inetd.conf file and then reinitializing inetd by sending it a SIGHUP signal. A less extreme approach might be to have your rwall daemon run as something other than root (the userid for running an inetd service is specified in inetd.conf), so that you can selectively disable its messages with "mesg n" (I haven't tried this approach, so I'm not 100% sure that it works). Cheers..Y -- Yoram Eisenstadter | Internet: yoram@cs.columbia.edu Columbia U., Dept. of Computer Science | UUCP: rutgers!columbia!cs!yoram 500 West 120th Street, Room 450 | Bitnet: yoram@cucsvm New York, NY 10027 | Phone: (212) 854-8180