Sponsored Content
Full Discussion: Modifying syslog.conf
Top Forums UNIX for Advanced & Expert Users Modifying syslog.conf Post 302373208 by goose25 on Thursday 19th of November 2009 06:07:37 PM
Old 11-19-2009
I have actually gotten past the point where the local system is now logging to the current.log file. Now I'm pointing some additional servers to the that server which will act as the loghost. When i check the log file, the only info there is for the local server and it's not logging for the remote hosts, which i believe is due to an rpc error. How can i fix this rpc error (find the cause of it and allow the remote logs to be written?)
 

10 More Discussions You Might Find Interesting

1. Red Hat

syslog.conf

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. Solaris

syslog-ng.conf

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

3. UNIX for Dummies Questions & Answers

Help confiuring syslog.conf

Hi, We had a hardware problem at work and none of the kernel problems outputted to the log file, just the screen. How can I configure the syslogd.conf file to record kernel events (ie hardware problems) to /dev/console and/var/log/messages. Can I just put: /dev/console /var/log/messages on... (5 Replies)
Discussion started by: mojoman
5 Replies

4. Red Hat

Modifying limits.conf & pam.d

Hello all, I'm running Oracle 10.2 on RHEL5. Current value of ulimit -n is set to a low value of 1024. I need to increase it to 65536 using the following procedure. cat >> /etc/security/limits.conf <<EOF oracle soft nproc 2047 oracle hard nproc 16384 oracle soft nofile 1024 oracle hard... (3 Replies)
Discussion started by: luft
3 Replies

5. Red Hat

problems after modifying modprobe.conf

Hey Guys, I am having a problem after modifying the modprobe.conf. I added a few entries for the HBA drivers. When I noticed that it would not boot after this, I mounted a knoppix disk and removed those lines from the modprobe.conf. Now after removing those lines, it is still stuck at the same... (2 Replies)
Discussion started by: s ladd
2 Replies

6. Shell Programming and Scripting

syslog.conf

How can i configure messages with warn priority to be logged in /var/log/mywarnings.log ? (1 Reply)
Discussion started by: g0dlik3
1 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. Red Hat

Configuring syslog.conf

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)
Discussion started by: manoj.solaris
2 Replies

9. BSD

Syslog.conf issue

I'm trying to get all ipfw logs going to ipfw.log I've managed that, but ipfw.log is also getting stuff that shows up in system.log !-ipfw *.notice;authpriv,remoteauth,ftp,install,internal.none /var/log/system.log kern.* /var/log/kernel.log... (5 Replies)
Discussion started by: jnojr
5 Replies

10. Solaris

Which are the available entries to forward syslog in syslog.conf?

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
elcsd.conf(5)							File Formats Manual						     elcsd.conf(5)

Name
       elcsd.conf - error logging configuration file

Description
       The  file  contains information used by the daemon to configure error logging for the system.  The system manager maintains this file.  The
       error logging daemon is dependent on the current order of the entries in the file.  Do not change the order.

       The information in the file shows any defaults and describes what you can enter.  A newline is used to delimit each entry in  the  file,  a
       null entry consists of a newline alone, and comments begin with #.
       #
       #    elcsd - errlog configuration file
       #

       {	   # delimiter DON'T remove or comment out!
       1	   # status 1-local,2-logrem,4-remlog,5-remlog+priloglocal
		   # errlog file size limit num. of blocks
       /usr/adm/syserr # errlog dir. path
		   # backup errlog dir. path
       /	   # single user errlog dir. path
       /usr/adm/syserr # log remote hosts errlog dir. path
		   # remote hostname to log to
       }	   # delimiter DON'T remove or comment out!
       #  hosts to log :S - separate file or :R - remotes file (together)
       remote1:S
       remote2:S
       #remote3:S	   # disabled
       remote4:S
	  .
	  .
	  .
       The status line of the file describes where you can log error packets, also called error messages:

	    Logs error packets locally =
		   1, the default.

	    Logs error packets from a remote system or systems to the local machine =
		   2.

	    Logs local and remote error packets locally =
		   3.

	    Logs error packets from the local system to a remote system =
		   4.

	    Logs error packets from the local system remotely and logs high
		   priority messages locally = 5.

       The  errorlog  file  size  defines  the	maximum size of an errorlog file.  If disk space is limited, you can specify the maximum number of
       blocks (512 bytes each) you want the errorlog file to be.  If you do not specify the maximum number of blocks, the system will  notify  you
       when the file system is 98% full.

       The  default  errorlog  directory path is You can direct error packets to a different directory; if you do, you must change the default for
       also. For further information, see

       If the error-logging daemon cannot write to the primary errorlog directory path, it attempts to log to the backup errorlog  directory  path
       automatically.

       The  root  directory  is  the default for the single-user errorlog directory path.  When the system makes the transition to multiuser mode,
       errors logged in single-user mode are transferred to the default errorlog directory path  You  can  direct  single-user	error  packets	to
       another directory.

       To log error packets from a remote system locally, set up an errorlog directory path on the local system.  The default is

       Errorlog  packets  from	remote systems can be logged to separate files or to one file.	S sets up a separate errorlog file for each remote
       system that logs locally.  R logs packets from the corresponding remote system to the file syserr.remotes.  The default is S.

Restrictions
       You must have superuser privileges to change the file.  However, anyone can view the file.

Files
       elcsd daemon messages

See Also
       elcsd(8), eli(8), uerf(8)
       Guide to the Error Logger System

																     elcsd.conf(5)
All times are GMT -4. The time now is 04:20 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy