(Apologies if this is in the archives, I searched for a while
and came up empty.)
Running on a 3000/300lx, DU 3.2D (but this manifested in
earlier revs, too.) I've set most logging in /etc/syslog.conf to pop
things out to the console as well as writing to /var/adm/sylog.dated;
such as
daemon.notice /dev/console
kern.debug /dev/console
mail.warning /dev/console
auth.info /dev/console
user.info /dev/console
syslog.info /dev/console
When syslogd restarts itself, or when I kill -HUP it, these
work fine, and I get things like
Jul 19 09:33:40 mysystem su: SU olc on /dev/ttyp9
appearing on the console. BUT, when the system first reaches runlevel
3 after a reboot or shutdown, syslogd starts up apparently without
reading (or maybe just ignoring) the information in /etc/syslog.conf,
i.e. I get no console information on (f'rinstance) root
logins/rshells, mail errors, etc. Once I HUP the process or it does
its daily restart, everything works the way it's supposed to.
I edited the startup to explicitly call /etc/syslog.conf, but
this made no difference. /etc is on / so it's not that it hasn't
mounted yet.
Any ideas? I'll summarize unless someone tells me that this
has been discussed/solved on the list before..
-Ole ("Scar") SI NON CONFECTVS NON REFICIAT
"Please get the shell archiver working," Tom said sharply.
---------------------------------------------------------------------
Ole Craig * olc_at_cs.umass.edu * (413)545-9674 voice, (413)545-1249 fax
CS Computing Facility * University of Massachusetts
<
http://www.cs.umass.edu/~olc/> for public key (or use finger)
Received on Fri Jul 19 1996 - 16:15:22 NZST