From: Mike Frysinger <vapier@gentoo.org>
To: Karel Zak <kzak@redhat.com>
Cc: util-linux@vger.kernel.org, Michal Kubecek <mkubecek@suse.cz>,
Petr Uzel <petr.uzel@suse.cz>
Subject: Re: flock in 2.20.1 can no longer lock the file it will execute
Date: Mon, 21 Nov 2011 15:11:19 -0500 [thread overview]
Message-ID: <201111211511.20270.vapier@gentoo.org> (raw)
In-Reply-To: <20111121163543.GU7916@nb.net.home>
[-- Attachment #1: Type: Text/Plain, Size: 232 bytes --]
On Monday 21 November 2011 11:35:43 Karel Zak wrote:
> Good idea, implemented and tested (git pull to get the change). It
> seems it works with your example as well as with NFSv4.
latest git now works for my scripts too :)
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2011-11-21 20:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-14 6:23 flock in 2.20.1 can no longer lock the file it will execute Mike Frysinger
2011-11-16 13:13 ` Karel Zak
2011-11-16 15:25 ` Mike Frysinger
2011-11-21 16:35 ` Karel Zak
2011-11-21 20:11 ` Mike Frysinger [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201111211511.20270.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=kzak@redhat.com \
--cc=mkubecek@suse.cz \
--cc=petr.uzel@suse.cz \
--cc=util-linux@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox