Sponsored Content
Operating Systems Solaris best configuration for syslog.conf Post 302712759 by DGPickett on Tuesday 9th of October 2012 04:40:15 PM
Old 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

can't find named.conf to configuration DNS

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

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

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

4. UNIX for Advanced & Expert Users

Modifying syslog.conf

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

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

6. Red Hat

Multipath.conf configuration max_fds

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

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

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

9. Red Hat

Grub.conf kernel field boot messages verbosity configuration

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

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
Net::Server::Log::Sys::Syslog(3)			User Contributed Perl Documentation			  Net::Server::Log::Sys::Syslog(3)

NAME
Net::Server::Log::Sys::Syslog - log via Syslog SYNOPSIS
use base qw(Net::Server::PreFork); __PACKAGE__->run( log_file => 'Sys::Syslog', syslog_ident => 'myapp', ); DESCRIPTION
This module provides Sys::Syslog logging to the Net::Server system. CONFIGURATION
log_file To begin using Sys::Syslog logging, simply set the Net::Server log_file configuration parameter to "Sys::Syslog". If the magic name "Sys::Syslog" is used, all logging will take place via the Sys::Syslog module. If syslog is used the parameters "syslog_logsock", "syslog_ident", and "syslog_logopt",and "syslog_facility" may also be defined. syslog_logsock Only available if "log_file" is equal to "Sys::Syslog". May be either unix, inet, native, console, stream, udp, or tcp, or an arrayref of the types to try. Default is "unix" if the version of Sys::Syslog < 0.15 - otherwise the default is to not call setlogsock. See Sys::Syslog. syslog_ident Only available if "log_file" is equal to "Sys::Syslog". Id to prepend on syslog entries. Default is "net_server". See Sys::Syslog. syslog_logopt Only available if "log_file" is equal to "Sys::Syslog". May be either zero or more of "pid","cons","ndelay","nowait". Default is "pid". See Sys::Syslog. syslog_facility Only available if "log_file" is equal to "Sys::Syslog". See Sys::Syslog and syslog. Default is "daemon". DEFAULT ARGUMENTS FOR Net::Server The following arguments are available in the default "Net::Server" or "Net::Server::Single" modules. (Other personalities may use additional parameters and may optionally not use parameters from the base class.) Key Value Default ## syslog parameters (if log_file eq Sys::Syslog) syslog_logsock (native|unix|inet|udp |tcp|stream|console) unix (on Sys::Syslog < 0.15) syslog_ident "identity" "net_server" syslog_logopt (cons|ndelay|nowait|pid) pid syslog_facility w+ daemon METHODS
"initialize" This method is called during the initilize_logging method of Net::Server. It returns a single code ref that will be stored under the log_function property of the Net::Server object. That code ref takes log_level and message as arguments and calls the initialized log4perl system. "handle_log_error" This method is called if the log_function fails for some reason. It is passed the Net::Server object, the error that occurred while logging and an arrayref containing the log level and the message. In turn, this calls the legacy Net::Server::handle_syslog_error method. LICENCE
Distributed under the same terms as Net::Server perl v5.18.2 2013-01-09 Net::Server::Log::Sys::Syslog(3)
All times are GMT -4. The time now is 09:18 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy