[13401] in Athena Bugs
Re: sun4 7.7R: syslogging on Solaris
daemon@ATHENA.MIT.EDU (jweiss@MIT.EDU)
Tue Apr 4 15:52:22 1995
From: jweiss@MIT.EDU
Date: Tue, 4 Apr 1995 15:52:09 -0400
To: Calvin Clark <ckclark@MIT.EDU>
Cc: bugs@MIT.EDU
In-Reply-To: [13391]
To the best of my knowledge syslogging has never worked correctly on
Athena Solaris machines.
A long time ago, it worked reasonably well, except that long syslog
messages were silently bitbucketed; sendmail 8 messages demonstrated
this failure rather well.
We took one or more patches from sun in an attempt to fix the problem.
I believe this resulted in the following situation (although I may be
describing an intermedaite step):
when you boot the machine syslogging doesn't seem to work. At some
point it may randomly start working, it may stop again later.
However, I know that a number of centrally logged messages have been
received from Solaris machines, so the problem may be better. I don't
know for sure. At some point I was told or noted that restarting
syslogd seems to solve the problem. My workstation now does this
automatically on boot, and I haven't had a problem since. (except
possibly missing some syslogs dutring the boot process, before I have
a chance to restart the syslogd.
For reference, /etc/rc2.d/s91local on my machine is:
#!/sbin/sh
# $Header: /afs/athena.mit.edu/user/j/w/jweiss/personal/mystation/config/RCS/S91local.tow,v 1.2 95/01/09 17:30:51 jweiss Exp $
PATH=/usr/bin:/bin
case $1 in
'start')
# restart syslogd so it works
kill `cat /etc/syslog.pid`
/usr/sbin/syslogd
# allow remote connections immediately
/usr/athena/bin/access_on
# reattach bitbucket
/bin/athena/detach -O bitbucket
/bin/athena/attach -L -n -h bitbucket
;;
'stop')
;;
*)
echo "usage: /etc/rc2.d/S91local {start|stop}"
;;
esac
