|
|
Sponsored Content
Top Forums
Shell Programming and Scripting
Parse out known messages from a log file
Post 302242333 by cdn2008 on Wednesday 1st of October 2008 04:47:34 PM
10-01-2008
|
|
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hello all,
I've got what I'm pretty sure is a simple problem, but I just can't seem to work past it. I'm trying to use awk to pretty up a log file, and calculate a percentage.
The log file looks like this:
# tail strtovrUsage
20090531-18:15:45 RSreq - 24, RSsuc - 24, RSrun - 78, RSerr -... (4 Replies)
Discussion started by: DeCoTwc
4 Replies
2. Shell Programming and Scripting
Hi,
I am working on the script to parsing the specific message like "aaaa" in multiple log files like N1-***,N2-***,N3-***...
The script is to find the list of lof files which contains the message "aaaa" and export the list into excel filE.
Can anyone give help?
Thanks (2 Replies)
Discussion started by: shyork2001
2 Replies
3. Shell Programming and Scripting
Hi all:
I'm working on a HPUX 11.23 system and I am needing to parse a tomcat-jakarta log file for memory use. Getting the desired data is easy, assuming the log file does not grow. This file grows constantly and I want to check it q 5 min. The next check will pick up from where it left off 5... (4 Replies)
Discussion started by: raggmopp
4 Replies
4. Shell Programming and Scripting
./abc.sh started at Sun Oct 24 06:42:04 PDT 2010
Message:
=======
Summary Report of NAME count
-----------------------------------------------------------------
Below is the output of the SQL query :-
NAME COUNT... (2 Replies)
Discussion started by: sandy1028
2 Replies
5. Shell Programming and Scripting
Hi all, thanks for reading the post.
I'm trying to parse hundreds of log files in a directory. One log file looks similar to below:
Investigator : Jim_Foo
Custodian : Jim_Foo-HDD1-FOO-1234
Export Path : N:\FOO-1234\Foo_Foo
Compute MD5 : No
File List Only: No
Extensions Selected:... (4 Replies)
Discussion started by: chipperuga
4 Replies
6. Shell Programming and Scripting
I was looking at this script which outputs the two lines which differs less than one sec.
#!/usr/bin/perl -w
use strict;
use warnings;
use Time::Local;
use constant SEC_MILIC => 1000;
my $file='infile';
## Open for reading argument file.
open my $fh, "<", $file or die "Cannot... (1 Reply)
Discussion started by: cele_82
1 Replies
7. Shell Programming and Scripting
Hello All,
Below is the excerpt from my Informatica log file which has 4 blocks of lines (starting with WRITER_1_*_1). Like these my log file will have multiple blocks of same pattern.
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 08 09:33:21 2014... (13 Replies)
Discussion started by: Ariean
13 Replies
8. Shell Programming and Scripting
I have a log file that's created daily by this command:
sar -u 300 288 >> /var/log/usage/$(date "+%Y-%m-%d")_$(hostname)_cpu.log
It that contains data like this:
Linux 3.16.0-4-amd64 (myhostname) 08/15/2015 _x86_64_ (1 CPU)
11:34:17 PM CPU %user %nice ... (12 Replies)
Discussion started by: unplugme71
12 Replies
9. Shell Programming and Scripting
I am developing one script which will take log file name, output file name, date, hour and minute as an argument and based on these inputs, the script will scan and capture all the error(s) that have been triggered from a given time. Example: script should capture all the error after 13:50 on Jan... (2 Replies)
Discussion started by: ROMA3
2 Replies
10. UNIX for Beginners Questions & Answers
Hi,
I want to parse below file and Write a function to extract the logs between two given timestamp.
Apache (Unix) Log Samples - MonitorWare
The challenge here is there are three date and time format.
First :- 07/Mar/2004:16:05:49
Second :- Sun Mar 7 16:02:00 2004
Third :- 29-Mar... (6 Replies)
Discussion started by: sahil_shine
6 Replies
LEARN ABOUT CENTOS
wd_keepalive
WD_KEEPALIVE(8) System Manager's Manual WD_KEEPALIVE(8) NAME
wd_keepalive - a simplified software watchdog daemon SYNOPSIS
wd_keepalive [-c filename|--config-file filename] DESCRIPTION
This is a simplified version of the watchdog daemon. If configured so it only opens .IR /dev/watchdog , and keeps writing to it often enough to keep the kernel from resetting, at least once per minute. Each write delays the reboot time another minute. After a minute of inactivity the watchdog hardware will cause a reset. In the case of the software watchdog the ability to reboot will depend on the state of the machines and interrupts. The wd_keepalive daemon can be stopped without causing a reboot if the device /dev/watchdog is closed correctly, unless your kernel is com- piled with the CONFIG_WATCHDOG_NOWAYOUT option enabled. Under high system load wd_keepalive might be swapped out of memory and may fail to make it back in in time. Under these circumstances the Linux kernel will reset the machine. To make sure you won't get unnecessary reboots make sure you have the variable realtime set to yes in the configuration file watchdog.conf. This adds real time support to wd_keepalive: it will lock itself into memory and there should be no problem even under the highest of loads. On system running out of memory the kernel will try to free enough memory by killing process. The wd_keepalive daemon itself is exempted from this so-called out-of-memory killer. OPTIONS
Available command line options are the following: -c config-file, --config-file config-file Use config-file as the configuration file instead of the default /etc/watchdog.conf. FILES
/dev/watchdog The watchdog device. /var/run/wd_keepalive.pid The pid file of the running wd_keepalive. SEE ALSO
watchdog.conf(5) watchdog(8) 4th Berkeley Distribution January 2005 WD_KEEPALIVE(8)