File::Tail::App looked interesting. It has a "lastrun_file" for repositioning in case of early script termination. It appears to record the offset of last processed record. But this does not seem to work. On a restart, it begins record from record 1 to force reprocessing of all data. I am sure that is not intended. I tried the example that was in the docs.
I dont have an email for Daniel Muey, the author. __________________________________________ Ranga Nathan / CSG Systems Programmer - Specialist; Technical Services; BAX Global Inc. Irvine-California Tel: 714-442-7591 Fax: 714-442-2840 Tim Wilde <[EMAIL PROTECTED]> Sent by: [EMAIL PROTECTED] 02/21/2006 12:00 PM To [email protected] cc Subject Re: [Boston.pm] daemonizing a perl script On Tue, 21 Feb 2006, Ranga Nathan wrote: > Thanks all for the responses.... > > While talking to my son he pointed out that tailing xferlog would be a > problem when the log is being rotated. I would be looking at an old inode > that has no activity. I looked at the system and found that the logs are > rotated at 4AM every sunday. So, I need to change my approach. > > I found a number of modules like File::Tail and File::Tail::App. Looks > like these modules will have the same issue. Actually, File::Tail is smart, it does all kinds of complicated determination of the normal average time between entries, and if it hasn't seen an entry in more than that amount of time, it'll assume the log got rotated away and close/re-open. Check out the Description section of the POD for more details: http://search.cpan.org/~mgrabnar/File-Tail-0.99.3/Tail.pm Tim Wilde -- Tim Wilde [EMAIL PROTECTED] Systems Administrator Dynamic Network Services, Inc. http://www.dyndns.com/ _______________________________________________ Boston-pm mailing list [email protected] http://mail.pm.org/mailman/listinfo/boston-pm _______________________________________________ Boston-pm mailing list [email protected] http://mail.pm.org/mailman/listinfo/boston-pm
