It appears that LogWatcher does not notice
modifications to a file that is accessed over NFS.
To reproduce, mount an NFS share on the machine
running Eclipse. Open a telnet (or however) session to
the NFS server machine and create a file "test.txt" with
some content.
In Eclipse, open the LogWatcher view and create a new
watcher on "test.txt" through the mounted NFS share.
Notice that it is shows the current content of the file.
Back on the NFS server machine, append new text
to "test.txt".
Notice that LogWatcher does not echo these additions.
This same behavior was reproduced using the
MKS "tail" utility, so it is likely specific to NFS.
One possible solution for LogWatcher would be to offer
an option where the file handle is closed and reopened
at regular intervals. This would likely workaround the
problem, but it is an untested proposal.
Logged In: YES
user_id=382762
I received this error in the eclipse log file when attempting to
watch a file over a Samba connection:
!ENTRY logwatcher 4 1 Jul 24, 2003 09:54:47.921
!MESSAGE Error reading from log file
!STACK 0
java.io.IOException: An unexpected network error occurred
at java.io.FileInputStream.readBytes(Native Method)
at java.io.FileInputStream.read
(FileInputStream.java:192)
at sun.nio.cs.StreamDecoder$CharsetSD.readBytes
(StreamDecoder.java:404)
at sun.nio.cs.StreamDecoder$CharsetSD.implRead
(StreamDecoder.java:442)
at sun.nio.cs.StreamDecoder.read
(StreamDecoder.java:179)
at java.io.InputStreamReader.read
(InputStreamReader.java:167)
at java.io.BufferedReader.fill
(BufferedReader.java:136)
at java.io.BufferedReader.readLine
(BufferedReader.java:299)
at java.io.BufferedReader.readLine
(BufferedReader.java:362)
at
org.graysky.eclipse.logwatcher.watchers.TextFileWatcher.run
(TextFileWatcher.java:124)
Logged In: NO
See the bug 1111421 created the 28/01/2005 by Christophe.