Sponsored Content
Full Discussion: syslogd - unable to log ?
Operating Systems AIX syslogd - unable to log ? Post 302263356 by ravager on Monday 1st of December 2008 11:23:49 AM
Old 12-01-2008
You have to create the file else it will not log
> /home/vilius/dir1/eeerrr.log
refresh -s syslogd
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

syslogd

Working out of AIX 4.3. All logs that were written via application suddenly stopped. executing a tail -f <logfile> was not producing any results. Tried to refresh the syslogd (daemon). When executing "refresh -s syslogd" system would display <<0513-036 The request could not be passed to... (2 Replies)
Discussion started by: buRst
2 Replies

2. Cybersecurity

HELP!!! syslogd is down...

Hi all My system logger has been down for the past 3 days... I am not able to get it to start from the terminal... /etc/init.d/syslogd start I am unable to find a log as to why it is failing!! Please advice where to look!!! I am totally lost here! Thanks in advance... KS (5 Replies)
Discussion started by: skotapal
5 Replies

3. UNIX for Advanced & Expert Users

multiple instances of syslogd - is it possible?

I would like to start up multiple instances of syslog daemon. I am having a little difficulty. Is this at all possible? I have separate syslog.conf1.... syslog.conf5 files. I have linked the daemon to separate files syslogd1 ... syslogd5 I have arranged the rcd.2 start/stop scripts for... (9 Replies)
Discussion started by: Gary Dunn
9 Replies

4. UNIX for Advanced & Expert Users

Syslogd

I have a remote syslog server which is recieving messages from many hosts. I would like it to log them in seperate files denoted by hostname . For example all messages for host1 in a directory of the same name. Is there an easy way to do this using syslogd? I have a feeling syslog-ng provides this... (3 Replies)
Discussion started by: silvaman
3 Replies

5. Solaris

Ignore events with syslogd

Hi friends, is it possible to ignore special messages with syslogd? we have some errors that are firmware issues an no real faults. we serach for a way to ignore ONLY these messages... OS is solaris 10... any ideas? tia, DN2 (1 Reply)
Discussion started by: DukeNuke2
1 Replies

6. Solaris

Restarting syslogd on Unix

Hi All, I can seem to find the syslog daemon in the /etc/init.d/ dir. i have made change to the syslog.conf i need to restart the daemon. am using solaris 10. i have no problem on version 9 Anyone with a template i can use for log review for auditing purposes. (1 Reply)
Discussion started by: lottiem
1 Replies

7. Linux

Message from syslogd

I'm recieving from time to time such messages: Message from syslogd@localhost at Sat Jul 8 18:29:58 2006 ... localhost kernel: Disabling IRQ #17 What could cause such messages? How can I at least disable these messages which are posted on all terminals? Note: $ uname -a Linux... (19 Replies)
Discussion started by: Hitori
19 Replies

8. AIX

Configure AIX syslogd

Hi Guys, I am configuring syslogd for Message broker. I know that we have to add a line user.* /var/log/wmb.log to the /etc/syslog.conf file. I want to know what userid does the user in user.* take? Thanks (1 Reply)
Discussion started by: vandi
1 Replies

9. Solaris

Syslogd

Hi , Iam using Solaris8 and as I checked I found syslogd process not running can please somebody suggest me the way to start it. (2 Replies)
Discussion started by: Laxxi
2 Replies

10. Solaris

Syslogd configuration

Where do I configure where syslogd writes to log files? I've got open files in an archive directory called errlog.131017 and audlog.131017 and, having run an fuser, it appears that syslogd is writing to these files. (3 Replies)
Discussion started by: psychocandy
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 03:01 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy