On Jan 7, 2008 3:55 PM, G T Smith
Mark Goldstein wrote:
Hi, ... I guess, it depends on what one wants to do with the logs. I used "tail" in a set of tests and found it very flexible and convenient. E.g. I did not want to know exactly in what log file the
<snip>
It always does :-)
If one is only filtering this is probably fine, as is the approach of using syslog suggested elsewhere ...
but the thing I am picking up here is the perl script is intended to talk to something else as well (a database backend by the look of it).
The Perl tail related modules offer a variety of options for performing this, Also without the need to call tail or any piping (e.g. File::Tail::App, Event::File::Tail, IO::Tail and File::Tail::FAM all seem to be possibilities here)....
Sure, I just gave one example where I thought "tail" was good enough and provided quick solution (not "quick and dirty"). I have to admit, I did not use "File::Tail" from pure ignorance and laziness :-). I'll definitely look into it next time I'll need to to something of this sort. Regards, -- Mark Goldstein -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org