Sponsored Content
Operating Systems Linux Red Hat syslog configuration and log lvl Post 302502865 by chipmunken on Wednesday 9th of March 2011 05:52:23 AM
Old 03-09-2011
solved it
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

syslog.log (HP-UX)

How can I setup the syslog.log file ? (2 Replies)
Discussion started by: salhoub
2 Replies

2. Linux

syslog configuration

Hi I have redhat linux v9.x. This is acting as a syslog server. I have a 1700 series cisco router I would like to log all the activity of my cisco router on my syslog server. Please anyone help me to configure it Regards, Raja (0 Replies)
Discussion started by: RajaRC
0 Replies

3. Shell Programming and Scripting

Finding your current run lvl

The title says it all really. I am writing a shell script for a Linux box, and I have recently run into a problem. I need to make sure I am at a certain run level first. Hence, the question. How can I find out what run level the box is currently running at? Is there a system variable... (2 Replies)
Discussion started by: Scripting Newb
2 Replies

4. Shell Programming and Scripting

A script for converting raid configuration log messages to ChangeLog files. ....

hi to all am new to shell scripting..itz very urgent. when i excuting the command metastat(raid configuration info) it will display some information. #metastat d1:submirror status: okey pass:1 d2:submirror staus:okey d3:submirror staus:error if staus is okey.no problem.once i... (0 Replies)
Discussion started by: arjunreddy3
0 Replies

5. UNIX for Dummies Questions & Answers

syslog.log - hp-ux

Hi, Following error message apeared in the syslog.log file of our hps2_dc server. Mar 10 17:22:12 hps2_dc vmunix: 0/4/0/0.1.3.255.14.1.0 sctl Mar 10 17:22:31 hps2_dc vmunix: 0/4/0/0: Unable to access previously accessed device at nport ID 0x10300. Could it be a hardware problem related... (4 Replies)
Discussion started by: mhbd
4 Replies

6. UNIX for Advanced & Expert Users

rotate modsec log with logrotate in the global configuration

Hello Experts, I have an apache 2.2.17 on solaris 10 that I am not sure if I, could list the following in the global settings in httpd.conf. I tested it in the Virtual host section of httpd.conf and, it works but, not sure if I can do it in the global settings. Any help would be greatly... (0 Replies)
Discussion started by: afadaghi
0 Replies

7. Solaris

best configuration for syslog.conf

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

8. HP-UX

HPUX syslog configuration

Hi all, We have few HPUX servers. Our monitoring server collects their CPU usage info, memory info and disk info in 5 min time interval. Now, problem is massive access log from monitoring server logged in syslog.log on all hpux servers. How can we prevent these access logs to be logged... (2 Replies)
Discussion started by: sembii
2 Replies

9. UNIX for Advanced & Expert Users

Apache log rotate configuration

HI i was trying to configure logrotate for my apache server and it's not working properly. here is my lodrotate configuration /var/log/httpd/*log { daily missingok notifempty sharedscripts compress delaycompress postrotate /sbin/service httpd... (1 Reply)
Discussion started by: bentech4u
1 Replies

10. Red Hat

Apache log rotate configuration

HI i was trying to configure logrotate for my apache server and it's not working properly. Os: Red Hat 6 here is my lodrotate configuration /var/log/httpd/*log { daily missingok notifempty sharedscripts compress delaycompress postrotate ... (3 Replies)
Discussion started by: bentech4u
3 Replies
syslog.conf(4)						     Kernel Interfaces Manual						    syslog.conf(4)

NAME
syslog.conf - syslogd configuration file SYNOPSIS
facility.severity destination Where: Is part of the system generating the message, specified in /usr/include/sys/syslog_pri.h. See also the syslogd(8) reference page. The severity level, which can be emerg, alert, crit, err, warning, notice, info, or debug. See /usr/include/sys/syslog_pri.h. The syslogd daemon logs all messages of the specified severity level plus all messages of greater severity. For example, if you specify level err, all messages of levels err, crit, alert, and emerg or panic are logged. A local file pathname to a log file, a host name for remote logging or a list of users. In the latter case the users will receive messages when they are logged in. An asterisk (*) causes a message to be sent to all users who are currently logged in. DESCRIPTION
The /etc/syslog.conf file is a system file that enables you to configure or filter events that are to be logged by syslogd. You can specify more than one facility and its severity level by separating them with semicolons. You can specify more than one facility logs to the same file by separating the facilities with commas, as shown in the EXAMPLES section. The syslogd daemon ignores blank lines and lines that begin with an octothorpe (#). You can specify # as the first character in a line to include comments in the file or to disable an entry. The facility and severity level are separated from the destination by one or more tab characters. If you want the syslogd daemon to use a configuration file other than the default, you must specify the file name with the following com- mand: # syslogd -f config_file Daily Log Files You can specify in the /etc/syslog.conf file that the syslogd daemon create daily log files. To create daily log files, use the following syntax to specify the path name of the message destination: /var/adm/syslog.dated/ { file} The file variable specifies the name of the log file, for example, mail.log or kern.log. If you specify a /var/adm/syslog.dated/file path name destination, each day the syslogd daemon creates a sub-directory under the /var/adm/syslog.dated directory and a log file in the sub-directory, using the following syntax: /var/adm/syslog.dated/ date / file Where: The date variable specifies the day, month, and time that the log file was created. The file variable specifies the name of the log file you previously specified in the /etc/syslog.conf file. The syslogd daemon automatically cre- ates a new date directory every 24 hours and also when you boot the system. The current directory is a link to the latest date directory. To get the latest logs, you only need to reference the /var/adm/syslog.dated/current directory. EXAMPLES
The following is a sample /etc/syslog.conf file: # # syslogd config file # # facilities: kern user mail daemon auth syslog lpr binary # priorities: emerg alert crit err warning notice info debug # kern.debug /var/adm/syslog.dated/kern.log user.debug /var/adm/sys- log.dated/user.log daemon.debug /var/adm/syslog.dated/daemon.log auth.crit;syslog.debug /var/adm/syslog.dated/syslog.log mail,lpr.debug /var/adm/syslog.dated/misc.log msgbuf.err /var/adm/crash.dated/msgbuf.savecore kern.debug /var/adm/messages kern.debug /dev/console *.emerg * FILES
/etc/syslog.conf /etc/syslog.auth - Authorization file for remote logging. /usr/include/sys/syslog_pri.h - Common components of a syslog event log record. RELATED INFORMATION
Commands: /usr/sbin/syslogd(8), /usr/sbin/binlogd(8) System Administration delim off syslog.conf(4)
All times are GMT -4. The time now is 12:07 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy