X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:message-id:subject:from:to:date:in-reply-to :references:content-type:mime-version:content-transfer-encoding; q=dns; s=default; b=icX6ROdXT0N8Tw0bsn9jbohIppKQxettwaUNQpRcG+s DV4KP6nUXc+gEpD+GamToEL6OxvjFk5nd3xnLqvyI3tuDxJQn6NHY+oBNrVnzImw oXJYiFzz+gUHSsdfRJDZXmL++RE5WHYTXqUFH78jOOr1CiaGyFKZQeEt4XIhBQSc = DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:message-id:subject:from:to:date:in-reply-to :references:content-type:mime-version:content-transfer-encoding; s=default; bh=oYZJSqe/DRMRGQhkHpsYsEhemEw=; b=YRnM664NUTLE0T0Rk kftlwkl2wkxJcxuaUh4lrlsoc/NsDx6Jk7snIhox72bPNmk2oY9Pq0WqBXwarB5G MjR60/o5PZ5MluHD5DMznuS/jTbyICWmw2ws5qrQINdekhlOjRxCo7ZhtijC59Kf wNs/pbRAfLWJRLDTGWlIoxWTCM= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-0.9 required=5.0 tests=BAYES_00,KAM_LAZY_DOMAIN_SECURITY,SPF_HELO_PASS autolearn=no version=3.3.2 spammy=H*M:cygwin, Success, timer, HContent-Transfer-Encoding:8bit X-HELO: mx1.redhat.com Message-ID: <41eec858fea3a796406875078fe63e55cdc39d79.camel@cygwin.com> Subject: Re: flock: cannot set up timer: Invalid argument From: Yaakov Selkowitz To: "cygwin AT cygwin DOT com" Date: Sat, 19 Jan 2019 23:10:27 -0600 In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: 8bit 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