01-09-2004
syslog.conf file and syslogd daemon
Hello,
I need a few information/explanation about system messages, syslog.conf file and syslogd daemon.
My problem is the following: I would like to log all system messages related to hardware problems into a particular file. For that, i have to add an entry in the syslog.conf file.
I know that i must add a line of the following type in the syslog.conf file:
facility.level /..../hardware.log
The problem is: what to put in the facility field (kern?, daemon? or something else).
Another problem is: once the configuration file has been modified, do i have to restart the syslogd daemon in order to have my modification taken into account?
The last question is: once the hardware related system messages will be logged in the file "hardware.log" what will they look like?
Thanks in advance for any answer
10 More Discussions You Might Find Interesting
1. Red Hat
Hi all
I have a RedHat Linux AS2.1 server that keep crashing/rebooting and there are no messages in the /var/log/messages file pointing to any problems. I had a look at the /etc/syslog.conf file to see what gets logged to /var/log/messages, but I don't know what else to add. Can anyone tell me... (1 Reply)
Discussion started by: soliberus
1 Replies
2. AIX
Hi All,
I am working on a server which has an /etc/syslog.conf file with the following entries (example):
local6.debug /dplogs/uss1udp001.log rotate size 1500m time 1d files 14
local7.debug /dplogs/uss1udp002.log rotate size 1500m time 1d files 14
-----------------------------... (3 Replies)
Discussion started by: jeffpas
3 Replies
3. Solaris
Has anyone here configured a central syslog server using syslog-ng ?
I have set one up and I'm trying to tune the syslog-ng.conf file, both for the server and the client. I have found lots of linux example files, but not much on Solaris which is slightly different.
So if you have a Solaris... (5 Replies)
Discussion started by: Tornado
5 Replies
4. Solaris
can anyone explain what is syslogd daemon in solaris. What is the use and how to start and stop the syslogd. (3 Replies)
Discussion started by: rogerben
3 Replies
5. Solaris
Hello Guys,
Do we need to configure this file only if we add SAN disk or even if we add local disk, do we need to modify? (4 Replies)
Discussion started by: mokkan
4 Replies
6. UNIX for Dummies Questions & Answers
Hi,
I have a question on /etc/syslog.conf file in Solaris 10.
Below is a line taken from /etc/syslog.conf file and I know that the last field (operator) is where the logs gets outputted but how do I find out what the output file name format is going to be and which directory it gets outputted... (1 Reply)
Discussion started by: stevefox
1 Replies
7. Shell Programming and Scripting
Hello there,
Guys I've got an issue and I need a hint...I have to parse /etc/syslog.conf file (under solaris) and need to get all path accordingly to all logs configured in there.
Bellow it's my syslog.conf file. If anybody knows more about this please let me know. Thanks .
#ident ... (2 Replies)
Discussion started by: catalint
2 Replies
8. Shell Programming and Scripting
How can i configure messages with warn priority to be logged in /var/log/mywarnings.log ? (1 Reply)
Discussion started by: g0dlik3
1 Replies
9. Solaris
I would like to configure the syslog.conf to have a good monitoring information about my system.
do you have any idea about best configuration from your experience in your Data Centers
BR, (5 Replies)
Discussion started by: maxim42
5 Replies
10. Solaris
Hi Community
Which are the available entries to forward syslog in syslog.conf
i have put
*.err;kern.debug;daemon.notice;mail.crit;user.alert;user.emerg;kern.notice;auth.notice;kern.warning @172.16.200.50
and it's not going through.giving error message like below:
syslogd:... (2 Replies)
Discussion started by: bentech4u
2 Replies
LEARN ABOUT OSF1
syslog.auth
syslog.auth(4) Kernel Interfaces Manual syslog.auth(4)
NAME
syslog.auth - authorization file for accepting remote syslog messages
SYNOPSIS
# format: Each fully qualified host name on a separate line hostname.domain_name
DESCRIPTION
The /etc/syslog.auth file specifies which remote hosts are allowed to forward syslog messages to the local host. For the sake of security,
only messages coming from remote hosts listed in the local /etc/syslog.auth file will be logged by the syslogd daemon.
If the /etc/syslog.auth file does not exist, then messages coming from any host will be accepted.
Each remote host name should appear in a separate line in /etc/syslog.auth. A line started with the # character is considered as a comment
and is thus ignored.
A host name must be a complete domain name such as trout.zk3.dec.com. If a domain host name is given, it must either appear in the local
/etc/hosts file or be able to be resolved by the local name server (BIND).
Note that a host name can have at most as many characters as defined by the MAXHOSTNAMELEN constant in <sys/param.h>, although each line
in the /etc/syslog.auth file can have up to 512 characters.
The /etc/syslog.auth file must be owned by root and has a permission of 0600.
To invoke a new version of the /etc/syslog.auth file, run the following command (as the super user) to initialize the syslogd daemon: kill
-HUP `cat /var/run/syslog.pid`
EXAMPLES
The following example provides a typical authorization file: # format: Each fully qualified host name on a separate line
c3poid.rvo.dec.com r2d2id.ckt.dec.com
FILES
Location of the authorization file.
RELATED INFORMATION
Commands: syslogd(8), syslog(1)
System Administration delim off
syslog.auth(4)