mbl900@uunet.uu.net (Mathew B Lim) (12/20/88)
Hi there, We had the same trouble with our SUN 4. Try editing the file /etc/syslog.conf and commenting out the line mail.debug ....... etc. this works for us. I suspect (although I am not 100% sure that this is a proper fix) that your machine is a standalone machine but has not been told that it is it's own loghost. Thus it tries to send some log messages (e.g. mail.debug messages) to an unknown `loghost' creating some sort of loop. Does this make sense? Anyway try the above fix and test it. (To test, try sending mail somewhere, this should send the syslogd wild if the above fix has not been done). Oh yes, after editing /etc/syslog.conf, you should kill syslogd and restart it.
pipes@nssdcs.gsfc.nasa.gov (David Pipes) (12/30/88)
There is another way to stop the syslogd from going when it wants to send mail.debug type messages to LOGHOST on a standalone. Just put this line at the top of the file (ie, as the first non-comment line): define(LOGHOST, 1) and you can get mail.debug messages, if you want them. This seems to tell the syslogd that the machine it is on is the loghost, but I am unsure how it does it. I believe this was posted here a while ago; It was passed on to me by several people to whom I am very grateful. BTW, the first line should include the word "crazy"; exact placement is left as an exercise for the reader. David Pipes
larry@uunet.uu.net (Larry Swift) (12/31/88)
munnari!anu.anu.oz.au!mbl900@uunet.uu.net (Mathew B Lim) writes: >above fix has not been done). Oh yes, after editing /etc/syslog.conf, you >should kill syslogd and restart it. Just do a "kill -1 `cat /etc/syslog.pid`". The syslogd daemon will re-scan the syslog.conf without losing messages. Larry Swift UUCP: {peora,uunet}!pdn!larry Paradyne Corp., LG-129 Phone: (813) 530-8605 P. O. Box 2826 Largo, FL, 34649-9981