Sponsored Content
Full Discussion: Syslogd
Top Forums UNIX for Advanced & Expert Users Syslogd Post 302085359 by muirhejs on Wednesday 16th of August 2006 08:01:58 PM
Old 08-16-2006
Not sure if this helps at all, but we use the Parse::Syslog perl module to normalize everything that comes in; we then load it into a database for referencing (Postgres, but any database should work).

From the documentation: http://search.cpan.org/dist/Parse-Sy...arse/Syslog.pm

Code:
 my $parser = Parse::Syslog->new( '/var/log/syslog', year => 2001);
 while(my $sl = $parser->next) {
     ... access $sl->{timestamp|host|program|pid|text} ...
 }

- John
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

syslogd

Working out of AIX 4.3. All logs that were written via application suddenly stopped. executing a tail -f <logfile> was not producing any results. Tried to refresh the syslogd (daemon). When executing "refresh -s syslogd" system would display <<0513-036 The request could not be passed to... (2 Replies)
Discussion started by: buRst
2 Replies

2. Cybersecurity

HELP!!! syslogd is down...

Hi all My system logger has been down for the past 3 days... I am not able to get it to start from the terminal... /etc/init.d/syslogd start I am unable to find a log as to why it is failing!! Please advice where to look!!! I am totally lost here! Thanks in advance... KS (5 Replies)
Discussion started by: skotapal
5 Replies

3. UNIX for Advanced & Expert Users

multiple instances of syslogd - is it possible?

I would like to start up multiple instances of syslog daemon. I am having a little difficulty. Is this at all possible? I have separate syslog.conf1.... syslog.conf5 files. I have linked the daemon to separate files syslogd1 ... syslogd5 I have arranged the rcd.2 start/stop scripts for... (9 Replies)
Discussion started by: Gary Dunn
9 Replies

4. Solaris

Ignore events with syslogd

Hi friends, is it possible to ignore special messages with syslogd? we have some errors that are firmware issues an no real faults. we serach for a way to ignore ONLY these messages... OS is solaris 10... any ideas? tia, DN2 (1 Reply)
Discussion started by: DukeNuke2
1 Replies

5. AIX

syslogd - unable to log ?

Hi, I wanted to log some authentication information, so I added following line to /etc/syslog.conf: auth.info /home/vilius/dir1/eeerrr.log After that I refreshed syslogd subsystem: refresh -s syslogd To check my logging I made few unsuccessfull attempts to login as root using ssh and... (1 Reply)
Discussion started by: vilius
1 Replies

6. Solaris

Restarting syslogd on Unix

Hi All, I can seem to find the syslog daemon in the /etc/init.d/ dir. i have made change to the syslog.conf i need to restart the daemon. am using solaris 10. i have no problem on version 9 Anyone with a template i can use for log review for auditing purposes. (1 Reply)
Discussion started by: lottiem
1 Replies

7. Linux

Message from syslogd

I'm recieving from time to time such messages: Message from syslogd@localhost at Sat Jul 8 18:29:58 2006 ... localhost kernel: Disabling IRQ #17 What could cause such messages? How can I at least disable these messages which are posted on all terminals? Note: $ uname -a Linux... (19 Replies)
Discussion started by: Hitori
19 Replies

8. AIX

Configure AIX syslogd

Hi Guys, I am configuring syslogd for Message broker. I know that we have to add a line user.* /var/log/wmb.log to the /etc/syslog.conf file. I want to know what userid does the user in user.* take? Thanks (1 Reply)
Discussion started by: vandi
1 Replies

9. Solaris

Syslogd

Hi , Iam using Solaris8 and as I checked I found syslogd process not running can please somebody suggest me the way to start it. (2 Replies)
Discussion started by: Laxxi
2 Replies

10. Solaris

Syslogd configuration

Where do I configure where syslogd writes to log files? I've got open files in an archive directory called errlog.131017 and audlog.131017 and, having run an fuser, it appears that syslogd is writing to these files. (3 Replies)
Discussion started by: psychocandy
3 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 POD ERRORS
Hey! The above document had some coding errors, which are explained below: Around line 104: You forgot a '=back' before '=head1' Around line 114: '=item' outside of any '=over' perl v5.16.2 2012-06-05 Net::Server::Log::Sys::Syslog(3)
All times are GMT -4. The time now is 12:59 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy