08-09-2006
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 what would the contents of the ideal /etc/syslog.conf file be. I want to log all the system related messages that one would need to do some proper troubleshooting.
10 More Discussions You Might Find Interesting
1. Linux
Hi everybody,
i have a little problem...
I have two server srv01 and srv02.
srv02 have a syslogd server onboard and listen on 515... not on 514 (it's busy).
How i configure the syslog.conf of srv01 for send logs on srv02:515 ???
Now i have on srv01:
*.* @srv02
if i write:
*.* ... (0 Replies)
Discussion started by: Zio Bill
0 Replies
2. Solaris
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
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. Solaris
Hi Everyone,
I just wanted to know about the below entry in syslog.conf in Solaris 10:
kern.notice @destserver
Now the log will be redirected to destserver. But I want to know the location on the destserver where this log will be thrown.
Thanks in Advance,
Deepak (4 Replies)
Discussion started by: naw_deepak
4 Replies
5. UNIX for Advanced & Expert Users
I have a RHEL box that I want to be the loghost for all of the other systems on my network and have set up a /logs partitions to hold all of the logs. I've also created a file called current.log that will contain daily logs and created it using the following command: cp /dev/null current.log. ... (4 Replies)
Discussion started by: goose25
4 Replies
6. Shell Programming and Scripting
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
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
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
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
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 DEBIAN
cgrulesengd
CGRULESENGD(8) libcgroup Manual CGRULESENGD(8)
NAME
cgrulesengd - control group rules daemon
SYNOPSIS
cgrulesengd [options]
DESCRIPTION
cgrulesengd is a daemon, which distributes processes to control groups. When any process changes its effective UID or GID, cgrulesengd
inspects the list of rules loaded from the cgrules.conf file and moves the process to the appropriate control group.
The list of rules is read during the daemon startup is are cached in the daemon's memory. The daemon reloads the list of rules when it
receives SIGUSR2 signal.
The daemon opens a standard unix socket to receive 'sticky' requests from cgexec.
OPTIONS
-h|--help
Display help.
-f <path>|--logfile=<path>
Write log messages to the given log file. When '-' is used as <path>, log messages are written to the standard output. If '-f' and
'-s' are used together, the logs are sent to both destinations.
-s[facility]|--syslog=[facility]
Write log messages to syslog. The default facility is DAEMON. If '-f' and '-s' are used together, the logs are sent to both destina-
tions.
-n|--nodaemon
Don't fork the daemon, stay in the foreground.
-v|--verbose
Display more log messages. This option can be used twice to enable more verbose log messages.
-q|--quiet
Display less log messages. This option can be used twice to enable even less log messages and to only log errors.
-Q|--nolog
Disable logging.
-d|--debug
Equivalent to '-nvvf -', i.e. don't fork the daemon, display all log messages and write them to the standard output.
-u <user>|--socket-user=<user>
-g <group>|--socket-group=<group> Set the owner of cgrulesengd socket. Assumes that cgexec runs with proper suid permissions so it
can write to the socket when cgexec --sticky is used.
FILES
/etc/cgrules.conf
the default libcgroup configuration file
SEE ALSO
cgrules.conf (5)
Linux 2009-02-18 CGRULESENGD(8)