[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Duplicity-talk] Usage of python fasteners on cygwin

From: Kenneth Loafman
Subject: Re: [Duplicity-talk] Usage of python fasteners on cygwin
Date: Tue, 8 Jun 2021 11:09:39 -0500

According to logs, since this commit five years ago:

commit 24d43cdf1bee0f4a53f629b7168e5f8705bc7d96
Author: Kenneth Loafman <kenneth@loafman.com>
Date:   Thu May 11 05:44:21 2017 -0500

    * Fixed bug #1320641 and others regarding lockfile
      - swap from lockfile to fasteners module
      - use an fcntl() style lock for process lock of duplicity cache
      - lockfile will now clear if duplicity is killed or crashes


On Tue, Jun 8, 2021 at 10:48 AM Scott Hannahs via Duplicity-talk <duplicity-talk@nongnu.org> wrote:
On Jun 8, 2021, at 02:53, imagenesis--- via Duplicity-talk <duplicity-talk@nongnu.org> wrote:

I want to use duplicity to manage NTFS backups from cygwin. There appears to be a problem with lockfiless because fasteners is using fnctl in operating the filesystems, and is unable to release because the object it acquires is not a valid lock:

It throws on release:

1. Do you know when Duplicity starting using fasteners? I think maybe it used something else in 0.6 because I dont remember if I always recieved locking errors. 
2. What is the intended/ideal implementation of fasteners on cygwin? 
3. Is cygwin suppose to behave like a POSIX filesystem or is the expected interaction with the FS for C/Python programs running in cygwin through the Win APIs?

It has used fasteners for quite awhile.  At least since I started building it on the Mac OS.


Duplicity-talk mailing list

reply via email to

[Prev in Thread] Current Thread [Next in Thread]