10-09-2012
Usually, the defaults are fine until you start debugging a problem. You can turn everything on for a new file for a limited time, and see what you do not want, turn that off and try again. Syslog is used by any application that thinks it is appropriate, but usually daemons of some sort, so it can be hard to generalize. Some tags are explicitly for detailed debug messages.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Help me!
I have problem.
I can't find named.conf file in /etc (Solaris 5.6,SPRAC)
Please! (1 Reply)
Discussion started by: nghia77
1 Replies
2. Red Hat
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
3. 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
4. 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
5. 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
6. Red Hat
Hi all,
I am looking at the specific configuration settings for multipath.conf on RHEL5.5.
In particular i was looking at the max_fds setting. Can anyone tell me the max number of open file descriptors that the RHEL5.5 system can have?
It has been set previously to 8192, and i was... (4 Replies)
Discussion started by: Tommyk
4 Replies
7. 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
8. 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
9. Red Hat
I am trying to understand what are the differences of boot messages verbosity levels for the kernel field in grub.conf
From my research, there appear to be three levels:
quiet
verbose
debug
I have also found documents that specify removing quiet from the kernel field. If this is done, is... (1 Reply)
Discussion started by: thaebich
1 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 CENTOS
memstomp
MEMSTOMP(1) General Commands Manual MEMSTOMP(1)
NAME
memstomp - detect function calls with overlapping memory regions
SYNOPSIS
memstomp [-dk] application [argument...]
memstomp -h
DESCRIPTION
The memstomp utility identifies function calls that use overlapping memory regions in situations when such an overlap is not allowed by
various standards. When a problem is detected, memstomp displays a backtrace to help you debug the problem, and if executed with the
--debug-info command line option, it even uses the available debugging information. Since the backtrace code is not thread safe, memstomp
also allows you to use the --kill option to immediately terminate the analyzed program when an invalid function call is detected.
This version of memstomp inspects the following function calls: memcpy(), memccpy(), mempcpy(), strcpy(), stpcpy(), strncpy(), stpncpy(),
strcat(), strncat(), wmemcpy(), wmempcpy(), wcscpy(), wcsncpy(), wcscat(), and wcsncat().
OPTIONS
-d, --debug-info
Make use of debugging information to produce more detailed stack traces.
-k, --kill
Kill the analyzed application when a problem is detected.
-h, --help
Display usage information and exit.
-q, --quiet
Be less verbose
SEE ALSO
memcpy(3), memccpy(3), mempcpy(3), strcpy(3), stpcpy(3), strncpy(3), stpncpy(3), strcat(3), strncat(3), wmemcpy(3), wmempcpy(3), wcscpy(3),
wcsncpy(3), wcscat(3), wcsncat(3)
AUTHORS
Lennart Poettering <lennart@poettering.net>
William Cohen <wcohen@redhat.com>
0.1.4 09 April 2013 MEMSTOMP(1)