Hi,
I'm trying to accomplish the following and would like some suggestions or possible bash script examples that may work
I have a directory that has a list of log files that's periodically dumped from a script that is crontab that are rotated 4 generations. There will be a time stamp that is... (4 Replies)
how to copy lines from a log file based on timestamp.
INFO (RbrProcessFlifoEventSessionEJB.java:processFlight:274) - E_20080521_110754_967: rbrAciInfoObjects listing complete!
INFO (RbrPnrProcessEventSessionEJB.java:processFlight:197) - Event Seq: 1647575217; Carrier: UA; Flt#: 0106; Origin:... (1 Reply)
Hi Xpert Out There
I have a lots of file in this path :
-rw-r----- 1 oracle dba 3954176 Dec 21 2006 1_2008.dbf
-rw-r----- 1 oracle dba 887808 Dec 21 2006 1_2009.dbf
-rw-r----- 1 oracle dba 143872 Dec 21 2006 1_2010.dbf
-rw-r----- 1 oracle dba ... (3 Replies)
Hi all.
I have a database log file in which log data get appended to it daily. I want to do a automatic maintainence of this log by going through the log and deleting lines belonging to a certain date.
How should i do it? Please help. Thanks.
Example. To delete all lines prior to Jun... (4 Replies)
Hello. I'm not nearly good enough with awk/perl to create the logfile scraping script that my boss is insisting we need immediately. Here is a brief 3-line excerpt from the access.log file in question (actual URL domain changed to 'aaa.com'):
209.253.130.36 - - "GET... (2 Replies)
I'm still up trying to figure this out and it is driving me nuts.
I have a log file which has a basic format of this...
2010-10-10 22:25:42
Init block 'UA Deployment Date': Dynamic refresh of repository scope variables has failed.
The ODBC function has returned an error. The database... (4 Replies)
Hi,
I have a csv file with old data..i need to have only last 30 days from the current dateof data in the file.The fourth field in the file is a date field.i need to write a script to delete the old data by comparing the the fourth field with the (current date -30).I need to delete the rows in... (2 Replies)
To delete log files content older than 30 days and append the lastest date log file date in the respective logs
I want to write a shell script that deletes all log files content older than 30 days and append the lastest log file date in the respective logs
This is my script
cd... (2 Replies)
Hello All !
I need your help on this case,
I have a csv file with this:
ITEM105;ARI FSR;2016-02-01 08:02;243
ITEM101;ARI FSR;2016-02-01 06:02;240
ITEM032;RNO TLE;2016-02-01 11:03;320
ITEM032;RNO TLE;2016-02-02 05:43;320
ITEM032;RNO TLE;2016-02-01 02:03;320
ITEM032;RNO... (2 Replies)
Dear Experts,
I have a log file that contains a timestamp, I would like to filter record from that file based on timestamp. For example refer below file -
cat sample.txt
Jan 19 20:51:48 mukul-Vostro-14-3468 systemd: pam_unix(systemd-user:session): session opened for user root by (uid=0)... (6 Replies)
Discussion started by: mukulverma2408
6 Replies
LEARN ABOUT REDHAT
time::local
Time::Local(3pm) Perl Programmers Reference Guide Time::Local(3pm)NAME
Time::Local - efficiently compute time from local and GMT time
SYNOPSIS
$time = timelocal($sec,$min,$hour,$mday,$mon,$year);
$time = timegm($sec,$min,$hour,$mday,$mon,$year);
DESCRIPTION
These routines are the inverse of built-in perl functions localtime() and gmtime(). They accept a date as a six-element array, and return
the corresponding time(2) value in seconds since the Epoch (Midnight, January 1, 1970). This value can be positive or negative.
It is worth drawing particular attention to the expected ranges for the values provided. The value for the day of the month is the actual
day (ie 1..31), while the month is the number of months since January (0..11). This is consistent with the values returned from local-
time() and gmtime().
The timelocal() and timegm() functions perform range checking on the input $sec, $min, $hour, $mday, and $mon values by default. If you'd
rather they didn't, you can explicitly import the timelocal_nocheck() and timegm_nocheck() functions.
use Time::Local 'timelocal_nocheck';
{
# The 365th day of 1999
print scalar localtime timelocal_nocheck 0,0,0,365,0,99;
# The twenty thousandth day since 1970
print scalar localtime timelocal_nocheck 0,0,0,20000,0,70;
# And even the 10,000,000th second since 1999!
print scalar localtime timelocal_nocheck 10000000,0,0,1,0,99;
}
Your mileage may vary when trying these with minutes and hours, and it doesn't work at all for months.
Strictly speaking, the year should also be specified in a form consistent with localtime(), i.e. the offset from 1900. In order to make
the interpretation of the year easier for humans, however, who are more accustomed to seeing years as two-digit or four-digit values, the
following conventions are followed:
o Years greater than 999 are interpreted as being the actual year, rather than the offset from 1900. Thus, 1963 would indicate the year
Martin Luther King won the Nobel prize, not the year 2863.
o Years in the range 100..999 are interpreted as offset from 1900, so that 112 indicates 2012. This rule also applies to years less than
zero (but see note below regarding date range).
o Years in the range 0..99 are interpreted as shorthand for years in the rolling "current century," defined as 50 years on either side of
the current year. Thus, today, in 1999, 0 would refer to 2000, and 45 to 2045, but 55 would refer to 1955. Twenty years from now, 55
would instead refer to 2055. This is messy, but matches the way people currently think about two digit dates. Whenever possible, use
an absolute four digit year instead.
The scheme above allows interpretation of a wide range of dates, particularly if 4-digit years are used.
Please note, however, that the range of dates that can be actually be handled depends on the size of an integer (time_t) on a given plat-
form. Currently, this is 32 bits for most systems, yielding an approximate range from Dec 1901 to Jan 2038.
Both timelocal() and timegm() croak if given dates outside the supported range.
IMPLEMENTATION
These routines are quite efficient and yet are always guaranteed to agree with localtime() and gmtime(). We manage this by caching the
start times of any months we've seen before. If we know the start time of the month, we can always calculate any time within the month.
The start times are calculated using a mathematical formula. Unlike other algorithms that do multiple calls to gmtime().
timelocal() is implemented using the same cache. We just assume that we're translating a GMT time, and then fudge it when we're done for
the timezone and daylight savings arguments. Note that the timezone is evaluated for each date because countries occasionally change their
official timezones. Assuming that localtime() corrects for these changes, this routine will also be correct.
BUGS
The whole scheme for interpreting two-digit years can be considered a bug.
The proclivity to croak() is probably a bug.
perl v5.8.0 2002-06-01 Time::Local(3pm)