Empty syslogs on Solaris

[jabr at blu.org (John Abreau)]

I'm finding that syslogd doesn't seem to be working right on any of the
Solaris machines at work. /srv/adm/messages comes up empty most of the
time; it appears that the only things ever to get logged are the boot-time
messages from dmesg. Oh, and sendmail logs correctly to /srv/log/syslog.

I've added extra rules to /etc/syslog.conf to log everything:

    *.info           /srv/adm/jabr/info
    *.alert          /srv/adm/jabr/alert
    *.notice         /srv/adm/jabr/notice
    *.err            /srv/adm/jabr/err
    *.debug          /srv/adm/jabr/debug
    *.crit           /srv/adm/jabr/crit
    *.emerg          /srv/adm/jabr/emerg

However, whether I send a SIGHUP to syslogd, or stop and restart it 
(sudo /etc/init.d/syslog stop ; sudo /etc/init.d/syslog start), it still
logs nothing. I'm using /bin/logger to try to create new log messages.

What am I missing here? Is syslogd on Solaris 7 broken? Should I be
looking for an open-source replacement?

--
John Abreau / Executive Director, Boston Linux & Unix 
Email: jabr at blu.org / URL: http://www.blu.org
ICQ#28611923 / AIM abreauj
-----------------------------------------------------------------------
"Working with NT is like trying to tune a watch wearing oven mitts.
 You can't get your fingers inside like you can with UNIX.
-----------------------------------------------------------------------

-
Subcription/unsubscription/info requests: send e-mail with
"subscribe", "unsubscribe", or "info" on the first line of the
message body to discuss-request at blu.org (Subject line is ignored).