License: BSD-3-Clause
URL: https://github.com/theckman/go-flock
Vcs-Browser:
https://salsa.debian.org/go-team/packages/golang-github-gofrs-flock
Description: thread-safe file locking library in Golang
flock implements a thread-safe sync.Locker interface for file locking.
It also
Description : platform independent file locking module
This package contains a single module, which implements a platform
independent file locking mechanism for Python. The lock includes a
lock counter and is thread safe. This means, when locking the same
lock object twice, it will not block.
This is
Description : easy API to file locking
Portalocker is a cross-platform library to provide
an easy API to file locking.
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.
Hi,
First of all, thanks for packaging this so fast. :)
Ok, I am very happy to help you :)
> The module is using fcntl(2), not flock(2).
>
Fixed.
> I'd use the wording from upstream's README which seems clearer. And it's
> probably worth mentioning that this supports reliable locking over N
bugs.debian.org
>
> * Package name: libfile-fcntllock-perl
> Version : 0.12
> Upstream Author : Jens Thoms Toerring
> * URL : http://search.cpan.org/dist/File-FcntlLock/
> * License : Artistic or GPL-1+
> Programming Lang: Perl
> Description
://search.cpan.org/dist/File-FcntlLock/
* License : Artistic or GPL-1+
Programming Lang: Perl
Description : Perl module for file locking with flock(2)
File::FcntlLock is a Perl module for file locking using fcntl(2) system call.
This module allow locks on a whole file or on some parts of it
.
Programming Lang: perl
Description : file locking with flock
File locking using the flock() call. If the file to be locked does not
exist, then the file is created. If the file was created then it will
be removed when it is unlocked assuming it's still an empty file.
.
Locks c
: Python
Description : Platform-independent file locking module
The lockfile module exports a FileLock class which provides a simple API for
locking files. Unlike the Windows msvcrt.locking function, the Unix
fcntl.flock, fcntl.lockf and the deprecated posixfile module, the API is
identical
[EMAIL PROTECTED] (Karl M. Hegbloom) writes:
> I think that it is probably fine like it is, except that it's not nfs
> safe without libnfslock. It could probably be rewritten some to call
> on our liblockfile, rather than doing it internally the way it does.
Does xemacs implement maillock itsel
> "Rob" == Rob Browning <[EMAIL PROTECTED]> writes:
Rob> Maybe you already knew this, but I just got around to looking
Rob> at the movemail source for emacs 20, and it really looks like
Rob> movemail already knows how to handle liblockfile. Check out
Rob> MAIL_USE_MAILLOCK and
[EMAIL PROTECTED] (Karl M. Hegbloom) writes:
> > "Rob" == Rob Browning <[EMAIL PROTECTED]> writes:
>
> Rob> Assuming you're right, and movemail is used for all mail
> Rob> locking, then if we patch movemail to use liblockfile, we
> Rob> should be fine.
>
> I volunteer to try rol
[EMAIL PROTECTED] (Karl M. Hegbloom) writes:
> I volunteer to try rolling those patches into XEmacs 20.5. I think
> that configure ought to detect `liblockfile' and compile `movemail'
> accordingly. Sound right?
Sounds good, but perhaps it should just fail to build on a debian
system if libl
> "Rob" == Rob Browning <[EMAIL PROTECTED]> writes:
Rob> Assuming you're right, and movemail is used for all mail
Rob> locking, then if we patch movemail to use liblockfile, we
Rob> should be fine.
I volunteer to try rolling those patches into XEmacs 20.5. I think
that configur
[EMAIL PROTECTED] (Karl M. Hegbloom) writes:
> I don't think that the dot locking done by `movemail' is nfs-aware.
> You'd need to use libnfslock for that, I guess, or patch `movemail'.
Assuming you're right, and movemail is used for all mail locking, then
if we patch movemail to use liblockfil
... more to say, now that I read what I wrote...
I don't think that the dot locking done by `movemail' is nfs-aware.
You'd need to use libnfslock for that, I guess, or patch `movemail'.
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] .
Trouble? e
> "Rob" == Rob Browning <[EMAIL PROTECTED]> writes:
Rob> OK, then I'll assume that we want to hack emacs to use
Rob> liblockfile. This requires repeatedly calling touchlock() to
Rob> keep the lockfile from being deleted during the period when
Rob> the lock is being held. I th
David Frey <[EMAIL PROTECTED]> writes:
> It isn't. The old policy mandated dot-lock, IIRC.
OK, then I'll assume that we want to hack emacs to use liblockfile.
This requires repeatedly calling touchlock() to keep the lockfile from
being deleted during the period when the lock is being held. I thi
On 18 Dec 1997, Rob Browning wrote:
> My question is, should I modify emacs to use maillock from liblockdev,
> or it the emacs mechanism OK (what about NFS)?
Note, that the policy requires you to use "libfilelock" (not "liblockdev"
which is just for devices) to lock mail folders--or implement a c
On Thu, Dec 18 1997 12:16 CST Rob Browning writes:
> /* On GNU/Linux systems, both methods are used by various mail
> programs. I assume that most people are using newer mailers that
> have heard of flock. Change this if you need to. */
>
> #define MAIL_USE_FLOCK
>
> And here's th
[EMAIL PROTECTED] (Mark W. Eichin) writes:
> I'll note that emacs19 does what was right at one point, *before*
> liblockfile was written; I don't know if they're compatible but figure
> that before debian 2.0 it would be safest to code up a fix. (Or steal
> your code from emacs20 :-)
My suspicio
I'll note that emacs19 does what was right at one point, *before*
liblockfile was written; I don't know if they're compatible but figure
that before debian 2.0 it would be safest to code up a fix. (Or steal
your code from emacs20 :-)
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "uns
My question is, should I modify emacs to use maillock from liblockdev,
or it the emacs mechanism OK (what about NFS)?
My reading is that emacs needs to be modified, but since liblockdev
requires you to call touchlock on a regular basis, I'm worried that
the modification might be non-trivial.
Her
On Tue, 24 Jun 1997, Philip Hands wrote:
> Hi,
>
> I noticed that during this discussion two issues that are not intrinsically
> related keep on getting tied together:
>
> 1) Reliable file locking, including over NFS
>
> 2) Reliable mail delivery to users' inbo
which is really what we want anyway.
+ [...]
+ no more grovelling
+ around for the system MDA and user's mailbox, no more worries about
+ whether the underlying OS supports file locking.
+
+ Also, the only way to lose mail vanished. If you specified localfolder
+ and the disk got full, your mail g
Philip Hands <[EMAIL PROTECTED]> writes:
> libmailaccess should be something like PAM for mail delivery,
> providing access to a user's mailbox by use of either Maildir, or
> dot-locking (via libnfslock say), or whatever other method --- as
> selected by the user.
Sounds good to me.
--
Rob
--
Hi,
I noticed that during this discussion two issues that are not intrinsically
related keep on getting tied together:
1) Reliable file locking, including over NFS
2) Reliable mail delivery to users' inboxes
I cannot claim to be an expert on NFS locking, but I have a fairly strong
fe
> "Christian" == Christian Schwarz <[EMAIL PROTECTED]> writes:
Christian> - Karl's "LockFile.pm"--a Perl implementation of
Christian> publib's lockfile (see
Christian> http://inetarena.com/~karlheg/Public)
It's not there anymore; I guess I can put it back up though. I'm not
reall
Hi folks!
I'm glad that so many people are finally involved in our "file locking
discussion". However, we had lots of discussions about this topic in the
past and we have no results, yet.
That's why I want to try to bring more "structure" into the discussion.
Hello!
I think that perhaps the easiest thing to do would be to just use the
procmail `lockfile' program to dot locking. It can be called from 'C'
with either `system' or `fork'/`exec*', and works well from scripts as
well. That's a quick and lazy way out.
Or, we could write our own small ut
In article <[EMAIL PROTECTED]>, Lars Wirzenius <[EMAIL PROTECTED]> wrote:
>However, I should point out at once that I don't know if my
>lockfile.c will work properly in all situations. I've done the
>best I can, based on manual pages, but I haven't been able to
>test it over NFS when various errors
On 18 Jun 1997, Karl M. Hegbloom wrote:
[snip]
> Christian> On 16 Jun 1997, Karl M. Hegbloom wrote:
>
> >> ** Publib looks like it might already be the library needing to
> >> be created that was mentioned earlier... or at least a very
> >> good start.
>
> Christian> Thanks f
> "Christian" == Christian Schwarz <[EMAIL PROTECTED]> writes:
Christian> Karl, thanks for the nice summary!
You're welcome. :-)
Christian> On 16 Jun 1997, Karl M. Hegbloom wrote:
>> ** Publib looks like it might already be the library needing to
>> be created that was menti
Karl, thanks for the nice summary!
On 16 Jun 1997, Karl M. Hegbloom wrote:
[snip]
> mis en place:
>
> I know that there are several stand-alone programs for handling
> file-locking, and that the `procmail' package has a fairly good setup
> for that. INND apparently d
Everything I know about file locking[1], I've learned from the short
chapter on it in "Beginning Linux Programming" (WROX Press), part of a
chapter that I've only skimmed in "UNIX Systems Programming for
SYSVr4" (O'Reilly), and from the manual pages to `fc
34 matches
Mail list logo
