Sponsored Content
Operating Systems HP-UX Getting error messages in syslog in HP-UX Post 302264161 by Mike1234 on Wednesday 3rd of December 2008 09:28:38 AM
Old 12-03-2008
Thanks. I will try to do that.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Date in syslog messages

Is there a way of configuring AIX syslog messages to include the year (not just month and day) (2 Replies)
Discussion started by: emilia
2 Replies

2. Shell Programming and Scripting

sort syslog messages

how can i sort the syslog message, so that the lastest time stamp show first , oldest show last. (1 Reply)
Discussion started by: 3Gmobile
1 Replies

3. UNIX for Advanced & Expert Users

error messages in /var/adm/messages

Hi, I have a SunFire V490, Solaris 10 with XP1024 storage and HP Library. I have noticed the following error messages in the /var/adm/messages file. These errors are being generated constantly. Also commands like devfsadm, format cfgadm etc are getting hung. After a reboot it works fine for a... (1 Reply)
Discussion started by: nitinp82
1 Replies

4. HP-UX

How to Redirect the error messages from Syslog file to our own Application Log File

Hello, I am New to Unix. I am Using HP-UX 9000 Series for my Application. I am Currently Facing an Issue that the error messages are being written in the syslog file instead of the Application Log File. The Codes for that Syslog.h is written in Pro*C. I want to know how to Redirect these... (3 Replies)
Discussion started by: balasubramaniam
3 Replies

5. Red Hat

syslog messages.

Good Day. Any idea on the messages log. it would be a great help to us. Upon checking the on the system logs, I found the following messages: EXT3-fs: INFO: recovery required on readonly filesystem. EXT3-fs: write access will be enabled during recovery. kjournald... (1 Reply)
Discussion started by: cabloy
1 Replies

6. Linux

Filter syslog messages.

Hello, How can we filter messages like : indrh03 sshd: Accepted publickey for score from 192.168.18.47 port 51034 ssh2 indrh03 sshd: pam_unix(sshd:session): session opened for user score by (uid=0) indrh03 sshd: pam_unix(sshd:session): session closed for user score such that they... (3 Replies)
Discussion started by: mahive
3 Replies

7. AIX

syslog messages

Hi Is there any setting in the syslog.conf that I can define a string to disable certain type of message that is generated in the message file for example I want to stop these type of messages getting generated. UnablAug 18 07:06:30 local1:warn|warning KCML: WARNING /usr/local/kcml/kcml... (3 Replies)
Discussion started by: antointoronto
3 Replies

8. AIX

Error messages in syslog

Hi, Can you please look into the below errors from syslog in AIX? And let me know is this a issue? How can I avoid these errors with out affecting my LPAR. Detail Data SYSLOG MESSAGE <27>Aug 23 08:24:28 syslog: slp: 0660-084 The SA failed to decode and compute received message:... (0 Replies)
Discussion started by: System Admin 77
0 Replies

9. Solaris

Syslog duplicate messages

I've heard that syslog in Solaris10 doesn't repeat duplicate messages and displays "last message repeated n times." Is there a way to increase the time interval, so that more messages are recognized as duplicates? thanks. (0 Replies)
Discussion started by: orange47
0 Replies

10. SuSE

Some error messages in var/log/messages

How are you? SUSE V10 and 11. In /var/log/messages I see these lines in some servers. I'd like to know what causes these errors and how to fix them. Thank you, error: PAM: Authentication failure for root from XXXXXXXX Did not receive identification string from XXXXXXX Invalid user suse-gm... (2 Replies)
Discussion started by: JDBA
2 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 08:42 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy