From: Yaakov Selkowitz <yselkowitz@cygwin.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: flock: cannot set up timer: Invalid argument
Date: Sun, 20 Jan 2019 05:10:00 -0000 [thread overview]
Message-ID: <41eec858fea3a796406875078fe63e55cdc39d79.camel@cygwin.com> (raw)
In-Reply-To: <AM6PR08MB3957781AA97C883116D985E2E99C0@AM6PR08MB3957.eurprd08.prod.outlook.com>
On Fri, 2019-01-18 at 07:11 +0000, Daniel Abrahamsson wrote:
> After upgrading from util-linux 2.25.2-2 to 2.32.1-1, flock started producing the following error message:
>
> flock: cannot set up timer: Invalid argument
>
> This is the test script I am using (which works under 2.25.2-2):
>
> #!/bin/bash --login
> (
> echo "Waiting for file lockâ
> flock -x -w 300 200 || exit 1
> echo âSuccessâ
> ) 200>test.lock
>
> Ideas?
This appears to be fixed in the latest snapshot.
--
Yaakov
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2019-01-20 5:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-18 7:12 Daniel Abrahamsson
2019-01-20 5:10 ` Yaakov Selkowitz [this message]
2019-01-21 7:11 ` Daniel Abrahamsson
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=41eec858fea3a796406875078fe63e55cdc39d79.camel@cygwin.com \
--to=yselkowitz@cygwin.com \
--cc=cygwin@cygwin.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).