➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author sandro.tosi
Recipients SilentGhost, eric.araujo, grobian, haubi, sandro.tosi, tarek
Date 2011-02-08.22:45:51
SpamBayes Score 3.4416578e-07
Marked as misclassified No
Message-id <AANLkTikWgKR8dnWh+vHOPmp9Q1UD_mY_74FqKDuxBL+E@mail.gmail.com>
In-reply-to <1297204857.1.0.636614880416.issue7719@psf.upfronthosting.co.za>
Content 
On Tue, Feb 8, 2011 at 23:40, Éric Araujo <report@bugs.python.org> wrote:
>
> Éric Araujo <merwok@netwok.org> added the comment:
>
> Do you have any pointer about those .nfs* files?  Are there other (build) tools that ignore them?  Is it always safe to skip .nfs* files, or only .nfs????? (i.e. six characters)?

Just replying for this part: .nfs* files are created by the nfs server
when on of its client removes a file while another client has the very
same file opened. the nfs server keeps the .nfs* file around until the
last client closes the file, after that it removes the .nfs* file.

About the number of digits after '.nfs' I'm not sure there's a
standard for it, but I saw files with more that 6 chars after that.

Regards,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi
History
Date User Action Args
2011-02-08 22:45:52sandro.tosisetrecipients: + sandro.tosi, tarek, eric.araujo, haubi, SilentGhost, grobian
2011-02-08 22:45:51sandro.tosilinkissue7719 messages
2011-02-08 22:45:51sandro.tosicreate