10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Dear folks
I have a map file of around 54K lines and some of the values in the second column have the same value and I want to find them and delete all of the same values. I looked over duplicate commands but my case is not to keep one of the duplicate values. I want to remove all of the same... (4 Replies)
Discussion started by: sajmar
4 Replies
2. AIX
Hi,
Can you please look into the below errors from syslog in AIX?
And let me know is this a issue? How can I avoid these errors with out affecting my LPAR.
Detail Data
SYSLOG MESSAGE
<27>Aug 23 08:24:28 syslog: slp: 0660-084 The SA failed to decode and compute received message:... (0 Replies)
Discussion started by: System Admin 77
0 Replies
3. Shell Programming and Scripting
Hi,
In a file, I have to mark duplicate records as 'D' and the latest record alone as 'C'.
In the below file, I have to identify if duplicate records are there or not based on Man_ID, Man_DT, Ship_ID and I have to mark the record with latest Ship_DT as "C" and other as "D" (I have to create... (7 Replies)
Discussion started by: machomaddy
7 Replies
4. IP Networking
Hello all,
Is it any way to filter or better do not capture at all, duplicate messages?
Thanks in advance (2 Replies)
Discussion started by: @dagio
2 Replies
5. AIX
Hi
Is there any setting in the syslog.conf that I can define a string to disable certain type of message that is generated in the message file
for example I want to stop these type of messages getting generated.
UnablAug 18 07:06:30 local1:warn|warning KCML: WARNING /usr/local/kcml/kcml... (3 Replies)
Discussion started by: antointoronto
3 Replies
6. Red Hat
Good Day.
Any idea on the messages log. it would be a great help to us. Upon checking the on the system logs, I found the following messages:
EXT3-fs: INFO: recovery required on readonly filesystem.
EXT3-fs: write access will be enabled during recovery.
kjournald... (1 Reply)
Discussion started by: cabloy
1 Replies
7. HP-UX
Hi,
I'm using HP-UX 11.11 on HP9000/800 PA-RISC system.I am getting the below messages daily in /var/adm/syslog/syslog.log file.Can someone help me out in this regard, why I am getting this messages & how to resolve it. I am using SSH version(HP-UX Secure Shell-A.04.20.004)
Messages:
Nov 26... (2 Replies)
Discussion started by: Mike1234
2 Replies
8. Shell Programming and Scripting
Hello Guys...
I am bit new to shell scripting and was looking for help !!
I have got syslog data on a linux server recording log messages from a device.
I need to seperate the data from log to file so that I can push it excell and get a report from that.
Log is in the format below
"... (2 Replies)
Discussion started by: raj_26apr
2 Replies
9. Shell Programming and Scripting
how can i sort the syslog message, so that the lastest time stamp show first , oldest show last. (1 Reply)
Discussion started by: 3Gmobile
1 Replies
10. Solaris
Few days ago I tried to fix an error in the crontab entry, basically I just add the complete path to run a script and remove an unused script from the crontab. I use crontab -e and mv FIFO FIFO.old command then cron start as cron won't start until I delete or move FIFO. I didn't know that using... (8 Replies)
Discussion started by: loeng
8 Replies
Parse::Syslog(3pm) User Contributed Perl Documentation Parse::Syslog(3pm)
NAME
Parse::Syslog - Parse Unix syslog files
SYNOPSIS
my $parser = Parse::Syslog->new( '/var/log/syslog', year => 2001);
while(my $sl = $parser->next) {
... access $sl->{timestamp|host|program|pid|text} ...
}
DESCRIPTION
Unix syslogs are convenient to read for humans but because of small differences between operating systems and things like 'last message
repeated xx times' not very easy to parse by a script.
Parse::Syslog presents a simple interface to parse syslog files: you create a parser on a file (with new) and call next to get one line at
a time with Unix-timestamp, host, program, pid and text returned in a hash-reference.
Constructing a Parser
new requires as first argument a source from where to get the syslog lines. It can be:
o a file-name for the syslog-file to be parsed.
o an IO::Handle object.
o a File::Tail object as first argument, in which case the read method will be called to get lines to process.
After the file-name (or File::Tail object), you can specify options as a hash. The following options are defined:
type Format of the "syslog" file. Can be one of:
syslog Traditional "syslog" (default)
metalog Metalog (see http://metalog.sourceforge.net/)
year Syslog files usually do store the time of the event without year. With this option you can specify the start-year of this log. If
not specified, it will be set to the current year.
GMT If this option is set, the time in the syslog will be converted assuming it is GMT time instead of local time.
repeat Parse::Syslog will by default repeat xx times events that are followed by messages like 'last message repeated xx times'. If you
set this option to false, it won't do that.
arrayref
If this option is true, next will return an array-ref instead of a hash-ref (and is thus a bit faster), with the following
contents:
0: timestamp
1: host
2: program
3: pid
4: text
locale Optional. Specifies an additional locale name or the array of locale names for the parsing of log files with national characters.
allow_future
If true will allow for timestamps in the future. Otherwise timestamps of one day in the future and more will not be returned (as a
safety measure against wrong configurations, bogus --year arguments, etc.)
Parsing the file
The file is parse one line at a time by calling the next method, which returns a hash-reference containing the following keys:
timestamp Unix timestamp for the event.
host Host-name where the event did happen.
program Program-name of the program that generated the event.
pid PID of the Program that generated the event. This information is not always available for every operating system.
text Text description of the event.
msgid Message numeric identifier, available only on Solaris >= 8 with "message ID generation" enabled".
facility Log facility name, available only on Solaris >= 8 with "message ID generation" enabled".
level Log level, available only on Solaris >= 8 with "message ID generation" enabled".
BUGS
There are many small differences in the syslog syntax between operating systems. This module has been tested for syslog files produced by
the following operating systems:
Debian GNU/Linux 2.4 (sid)
Solaris 2.6
Solaris 8
Report problems for these and other operating systems to the author.
COPYRIGHT
Copyright (c) 2001, Swiss Federal Institute of Technology, Zurich. All Rights Reserved.
LICENSE
This module is free software; you can redistribute it and/or modify it under the same terms as Perl itself.
AUTHOR
David Schweikert <dws@ee.ethz.ch>
HISTORY
2001-08-12 ds 0.01 first version
2001-08-19 ds 0.02 fix 'last message repeated xx times', Solaris 8 problems
2001-08-20 ds 0.03 implemented GMT option, year specification, File::Tail
2001-10-31 ds 0.04 faster time parsing, implemented 'arrayref' option, better time-increment algorithm
2002-01-29 ds 0.05 ignore -- MARK -- lines, low-case months, space in program names
2002-05-02 ds 1.00 HP-UX fixes, parse 'above message repeats xx times'
2002-05-25 ds 1.01 added support for localized month names (uchum@mail.ru)
2002-10-28 ds 1.02 fix off-by-one-hour error when running during daylight saving time switch
2004-01-19 ds 1.03 do not allow future dates (if allow_future is not true)
2004-07-11 ds 1.04 added support for type 'metalog'
2005-12-24 ds 1.05 allow passing of a IO::Handle object to new
perl v5.12.3 2007-12-30 Parse::Syslog(3pm)