https://sourceforge.net/p/fetchlog/feature-requests/Recent changes to feature-requestsenWed, 10 Jan 2007 17:49:21 -0000https://sourceforge.net/p/fetchlog/feature-requests/2/<div class="markdown_content"><p>Need to handle rotation of logs and use fethlog to parse prvious log if rotation has occured between runs.</p></div>AnonymousWed, 10 Jan 2007 17:49:21 -0000https://sourceforge.neta5eb22ab2ca2ee3c2830645c15408e4887ebf1f9https://sourceforge.net/p/fetchlog/feature-requests/1/<div class="markdown_content"><p>Hello,</p> <p>Thanks for your great work.</p> <p>Here is my problem : When the monitored logfile size is <br /> returning to zero (for example after a reboot or restart of <br /> a process), fetchlog bookmark file keeps watching too <br /> far in the file, so no matches are returned while the new <br /> file is shorter than before...</p> <p>Workaround : manually clear bookmark files. However <br /> this is a bit fragile as the process generating the logfile <br /> could be stop/start without being notified... So I can not <br /> know exactly when to clear the bookmark file.</p> <p>Maybe there is another method. Maybe I'm missing <br /> something...</p> <p>Solution : <br /> 1) Easy but not 100% reliable : If the file length is below <br /> bookmark file, bookmark file should be reset<br /> 2) Harder but 98% reliable : If the start of the file (5000 <br /> first bytes) is different from one check to another, reset <br /> bookmark file.<br /> How to check 5000 first bytes without keeping 5000 <br /> bytes =&gt; use MD5 or other checksum method to <br /> compare. Keep only checksum in the bookmark file.<br /> 3) 99,9% reliable, check 5000 bytes not from the start, <br /> check from the "last 5000 bytes" in the file (just before <br /> the bookmark)</p> <p>thank you.</p> <p>mail : <br /> patrick.lepoutre@pimkie.fr</p></div>AnonymousMon, 10 Oct 2005 09:22:28 -0000https://sourceforge.netadf1490b660f87817c86154a10148d5f3d354383