![]() |
|
|
|
|
|||||||
| Forums | Portal | Register | Forum Rules | FAQ | Contribute | Members List | Arcade | Search | Today's Posts | Mark Forums Read |
| Linux RedHat, Ubuntu, SUSE, Fedora, Debian, Mandriva, Slackware, Gentoo linux, PCLinuxOS. All Linux questions here! |
|
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| syslog-ng.conf | Tornado | SUN Solaris | 5 | 5 Days Ago 04:20 AM |
| Configuring snmpd.conf and snmptrapd.conf | jagdish.machhi@ | UNIX for Advanced & Expert Users | 2 | 04-17-2008 12:01 PM |
| Configuring syslog.conf in a TRU64 UNIX machine | adak2010 | UNIX for Dummies Questions & Answers | 0 | 04-11-2008 01:45 AM |
| syslog.conf file and syslogd daemon | VeroL | UNIX for Dummies Questions & Answers | 1 | 01-09-2004 07:05 AM |
| Severity Level in syslog.conf | dookeobih | UNIX for Dummies Questions & Answers | 3 | 12-12-2001 01:02 AM |
|
|
Submit Tools | LinkBack | Thread Tools | Display Modes |
|
#1
|
|||
|
|||
|
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. |
| Forum Sponsor | ||
|
|
|
#2
|
||||
|
||||
|
It depends on your exact logging needs, but the easiest way to capture *everything* is to add a line such as
Code:
*.debug /var/log/everything Cheers ZB |
||||
| Google The UNIX and Linux Forums |