It is creating a log file that grows to a specified size and then starts writing back at 0 again.
I want to be able to continously read this log file, determine when it has reset it's pointer and then read from the top again. I need to then send this information off via syslog to another server.
Any ideas?
Dave -- Saving the world one node at a time
In reply to Reading log files that get overwritten by Zapawork
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |