Hi all,
Thanks to those below for the replies:
Edward Philip
Craig Raskin
Dan Brown
Karl Vogel
Sean Quaint
Robert Johannes
Michael Salehi
Eric Pancer
The consensus was that the white space used in syslog.conf was being
place in
as spaces, NOT tabs.
I did recheck this, and all the whitespace in syslog.conf are tabs.
I also made sure the files to log to were already in place with the
touch command.
Some entries I attempt to place in the syslog.conf to segregate logging
still doesnt work.
The Solaris 7 man page makes references to the conf file being
preprocessed by
the m4 preprocessor, hence my reference in the initial question.
Ill show examples of what Im trying to do below:
kern.* /var/log/kernel
Now to me, this indicates that any log-level relating to the kernel
should go
into this file. This file exsists, and has the same permissions as the
syslog
or messages file.
When I run syslog -d, I see the following:
# syslogd -d
getnets() found 1 addresses, the are: 0.0.0.0.2.2
amiloghost() testing 63.73.223.70.2.2
I am loghost
cfline(*.err;kern.notice;auth.notice
/dev/sysmsg)
cfline(*.err;kern.debug;daemon.notice;mail.crit
/var/adm/messages)
cfline(auth.info
/var/adm/authlog)
cfline(*.alert;kern.err;daemon.err
operator)
cfline(*.alert
root)
cfline(*.emerg
*)
cfline(mail.debug
/var/log/syslog)
cfline(kern.*
/var/log/kernel)
syslogd: line 44: unknonwn priority name "*"
started: .......................
syslogd continues to run, but refuses to acknowledge the new entry.
Ill keep trying and will post another summary when I get this resolved.
Thanks again.,
Morgan
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:13:26 CDT