Re^3: Parsing a specific section of a log file

The reason I suggested Time::Local, though: if your dates are all identicaly shapped and speed is an issue (which it may be at 5 minute intervals) then it's like a million times faster to use timelocal_nocheck. It's more work too, but it can be worth it in some situations.

Er, I guessed ParseDate was from Date::Manip.

-Paul

Comment on Re^3: Parsing a specific section of a log file Select or Download Code

Replies are listed 'Best First'.
Re^4: Parsing a specific section of a log file by been42 (Curate) on Feb 28, 2007 at 22:31 UTC
Yep, that's the ParseDate from Date::Manip. Some work popped up in the middle of posting and I forgot to put everything in there. We run our script a few times a day, but I'm not sure if ParseDate would be fast enough to process data in time for you to do anything useful with it in a 5-minute window. It's just what we use at work because we have to deal with so many date formats in different files. Also because we're about 50% people who like 'MM/DD/YYYY' dates and 50% people who like 'YYYY-MM-DD' dates, and ParseDate was the easiest way to resolve that conflict.	[reply]

Replies are listed 'Best First'.

Re^4: Parsing a specific section of a log file
by been42 (Curate) on Feb 28, 2007 at 22:31 UTC

Yep, that's the ParseDate from Date::Manip. Some work popped up in the middle of posting and I forgot to put everything in there. We run our script a few times a day, but I'm not sure if ParseDate would be fast enough to process data in time for you to do anything useful with it in a 5-minute window. It's just what we use at work because we have to deal with so many date formats in different files. Also because we're about 50% people who like 'MM/DD/YYYY' dates and 50% people who like 'YYYY-MM-DD' dates, and ParseDate was the easiest way to resolve that conflict.

[reply]