i’d like to “Tail -f” a lot of logfiles from within a java app.
I’ve gotten this to work by monitoring the size and last update and repeatedly opening the file and reading the last few bytes whenever the file size or last update time changes–then closing it right away.
This seems problematic because I might have it open when the logger decides to rename the file which will cause some kind of problem.
I’d also like to detect a “Rolled” file with a mechanism more sure than noticing that the file size reduced… seems error prone but unlikely.
Since I don’t seem to have access to the file descriptor or other low-level file utilities I may not be able to reproduce tail’s behavor–but are there any tricks to reading a file without “Locking” it for rename/delete (Windows 7)
I guess another possibility is to actually spawn a tail -f process and read the process output, but that seems somewhat heavy–I’m scanning like 60 logfiles here, some of which have a lot of output (Most will be idle).
Apache Commons has a Tailer class, would that do what you want? If it would, it has rolling detection mechanism as well as the reading stuff, so you’d get all you need.
If that cannot do it, it might be that there’s no way of doing it with pure java. You’d need some help of, for example, C code, utilizing fopen with SH_DENYNO parameter allowing shared open on windows. Or then just call a tail implementation by executing a system command.
But since the code opening the log file is the one causing the lock on it, even that might not help. In that case the only real option is to change the way your logging works, as that is the culprit locking the file. Log4j can use a SocketAppender, among other things.