🚀 go-pugleaf

No Unfortunately I dont have control of the
program that writes the logfile, in that case I wouldn't have
this problem at all


Anything other suggestions ?



Da-Shar <johnlee128@hotmail.com> skrev i en
nyhedsmeddelelse:8495nn$mo4$1@oak.prod.itd.earthlink.net...
> If you have control over the program which creates the log file, I would
> suggest that the log file be written in fixed length record.  You may
waste
> some space, but you gain a lot of speed.  With fixed length record, you
> should be able to jump to the record you wanted.
>
> Please read the help on Put/Get statement.
>
> Nick Jensen <race.nkj@get2net.dk> wrote in message
> news:g5S94.514$iq6.800@news.get2net.dk...
> > At my work there's a little application running 24 hours 365 days of the
> > year
> > always writing a log file of some radio "data" transmission. I'ts all
> doing
> > a
> > nice job, except for a few lines in the log needs to be processed by
some
> > 3rd party software (which I'm working on :)). The problem is really the
> log
> > file itself , which is VERY large !, around 43.000 lines every 24 hours,
> of
> > course depending on the radio "Traffic" !. Every time a new line is
> > written to the log file I want my little program called "Logwatcher" to
> read
> > the line !, let's say the logfile is 33.000 lines BIG, and now is
written
> > lines 33.000 to 33.017 , I want to read only the last added 17 lines ??
> >
> > How can I Do that , in smart and FAST way ??
>
>
>
>