I have not tried this, it is not tested, but an idea you could pursue:
syslogd can send messages either to a file (this is the common case), to another host or to a users terminal. For instance: to send all mail and daemon messages of priority crit and above to user xxx enter the following line into /etc/syslog.conf:
You could probably create an user account, have it run some script which waits for terminal input and does something according to the sort of input it receives. The create an entry in /etc/syslog.conf to have this user receive all the messages you want to track.
i don't know if you could specify several destinations so maybe your script will have to do the log writing syslog normally does by itself.
In any case i would be intereseted to hear your solution.
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... (1 Reply)
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)
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)
i have this script which works fine but shows errors when it runs..these are more like warnings and the script runs fine.. i am on a sun machine.. i know it writes all the error messages to a master log file.. is there any way i can turn off these warnings/error messages and prevent them from being... (2 Replies)
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)
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)
Hi,
I would like to configure syslog linux client, syslog server is windows server.
so adding on linux client in /etc/syslog.conf @hostname will work in the place of directory location.
example of /etc/syslog.conf
# Log all kernel messages to the console.
# Logging much else clutters up... (2 Replies)
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 BSD
syslogd
SYSLOGD(8) System Manager's Manual SYSLOGD(8)NAME
syslogd - log systems messages
SYNOPSIS
syslogd [ -fconfigfile ] [ -mmarkinterval ] [ -d ]
DESCRIPTION
Syslogd reads and logs messages into a set of files described by the configuration file /etc/syslog.conf. Each message is one line. A
message can contain a priority code, marked by a number in angle braces at the beginning of the line. Priorities are defined in <sys/sys-
log.h>. Syslogd reads from the UNIX domain socket /dev/log, from an Internet domain socket specified in /etc/services, and from the spe-
cial device /dev/klog (to read kernel messages).
Syslogd configures when it starts up and whenever it receives a hangup signal. Lines in the configuration file have a selector to deter-
mine the message priorities to which the line applies and an action. The action field are separated from the selector by one or more tabs.
Selectors are semicolon separated lists of priority specifiers. Each priority has a facility describing the part of the system that gener-
ated the message, a dot, and a level indicating the severity of the message. Symbolic names may be used. An asterisk selects all facili-
ties. All messages of the specified level or higher (greater severity) are selected. More than one facility may be selected using commas
to separate them. For example:
*.emerg;mail,daemon.crit
Selects all facilities at the emerg level and the mail and daemon facilities at the crit level.
Known facilities and levels recognized by syslogd are those listed in syslog(3) without the leading ``LOG_''. The additional facility
``mark'' has a message at priority LOG_INFO sent to it every 20 minutes (this may be changed with the -m flag). The ``mark'' facility is
not enabled by a facility field containing an asterisk. The level ``none'' may be used to disable a particular facility. For example,
*.debug;mail.none
Sends all messages except mail messages to the selected file.
The second part of each line describes where the message is to be logged if this line is selected. There are four forms:
o A filename (beginning with a leading slash). The file will be opened in append mode.
o A hostname preceeded by an at sign (``@''). Selected messages are forwarded to the syslogd on the named host.
o A comma separated list of users. Selected messages are written to those users if they are logged in.
o An asterisk. Selected messages are written to all logged-in users.
Blank lines and lines beginning with `#' are ignored.
For example, the configuration file:
kern,mark.debug /dev/console
*.notice;mail.info /usr/spool/adm/syslog
*.crit /usr/adm/critical
kern.err @ucbarpa
*.emerg *
*.alert eric,kridle
*.alert;auth.warning ralph
logs all kernel messages and 20 minute marks onto the system console, all notice (or higher) level messages and all mail system messages
except debug messages into the file /usr/spool/adm/syslog, and all critical messages into /usr/adm/critical; kernel messages of error
severity or higher are forwarded to ucbarpa. All users will be informed of any emergency messages, the users ``eric'' and ``kridle'' will
be informed of any alert messages, and the user ``ralph'' will be informed of any alert message, or any warning message (or higher) from
the authorization system.
The flags are:
-f Specify an alternate configuration file.
-m Select the number of minutes between mark messages.
-d Turn on debugging.
Syslogd creates the file /var/run/syslog.pid, if possible, containing a single line with its process id. This can be used to kill or
reconfigure syslogd.
To bring syslogd down, it should be sent a terminate signal (e.g. kill `cat /var/run/syslog.pid`).
FILES
/etc/syslog.conf the configuration file
/var/run/syslog.pid the process id
/dev/log Name of the UNIX domain datagram log socket
/dev/klog The kernel log device
SEE ALSO logger(1), syslog(3)4.2 Berkeley Distribution November 16, 1996 SYSLOGD(8)