Mailing-List: contact issues-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: issues@commons.apache.org
Date: Fri, 8 Jun 2012 01:37:23 +0000 (UTC)
From: "Niall Pemberton (JIRA)" <jira@apache.org>
To: issues@commons.apache.org
Message-ID: <1613296045.51056.1339119443576.JavaMail.jiratomcat@issues-vm>
In-Reply-To: 
 <2009443376.46647.1302368465830.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (IO-269) Tailer locks file from deletion/rename
 on Windows
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/IO-269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13291490#comment-13291490 ] 

Niall Pemberton commented on IO-269:
------------------------------------

Do you have any benchmark to back up the less efficient statement? Marcos indicated that it was not the case in his benchmark.

Continuing to tail a file thats been renamed would be a bug (log files is a good example of that).

The current implementation can miss rotations - thats a factor of the delay and how fast/frequently the file is being written to. So the question really is, is it more likely to miss rotations and I believe that goes back to the efficiency question.
                
> Tailer locks file from deletion/rename on Windows
> -------------------------------------------------
>
>                 Key: IO-269
>                 URL: https://issues.apache.org/jira/browse/IO-269
>             Project: Commons IO
>          Issue Type: Bug
>            Reporter: Sebb
>         Attachments: IO-269-v2.patch, IO-269.patch
>
>
> The Tailer code works on Windows, except that it locks the file against deletion or rename.
> The test code fails to detect this, because it fails to check if the file deletion succeeds.
> This seems to be a Windows OS issue.
> A possible solution might be to keep closing and re-opening the file.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira