From owner-freebsd-security@freebsd.org  Tue Oct 24 15:31:53 2017
Return-Path: <owner-freebsd-security@freebsd.org>
Delivered-To: freebsd-security@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 572D8E50C83;
 Tue, 24 Oct 2017 15:31:53 +0000 (UTC)
 (envelope-from borjam@sarenet.es)
Received: from cu01176b.smtpx.saremail.com (cu01176b.smtpx.saremail.com
 [195.16.151.151])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 1BAB1643D2;
 Tue, 24 Oct 2017 15:31:52 +0000 (UTC)
 (envelope-from borjam@sarenet.es)
Received: from [172.16.8.41] (unknown [192.148.167.11])
 by proxypop01.sare.net (Postfix) with ESMTPA id 777009DCA56;
 Tue, 24 Oct 2017 17:31:49 +0200 (CEST)
Content-Type: text/plain;
	charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 11.0 \(3445.1.7\))
Subject: Re: Periodic jobs lockf timeout
From: Borja Marcos <borjam@sarenet.es>
In-Reply-To: <1508858729.34364.32.camel@freebsd.org>
Date: Tue, 24 Oct 2017 17:31:48 +0200
Cc: Alan Somers <asomers@freebsd.org>,
 "freebsd-hackers@freebsd.org" <freebsd-hackers@freebsd.org>,
 freebsd-security@freebsd.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <D12E3AF6-9842-4B64-8E60-29748E519DBE@sarenet.es>
References: <AEF2CF7D-BFAC-4ACE-95F2-EF5026E89959@sarenet.es>
 <CAOtMX2hb_Ur8XtTdoPju3ZQGMfJ_pApUKsZiaocxaG9n+DVycA@mail.gmail.com>
 <EAE33C61-BC70-4A09-86A0-0C5F62D993ED@sarenet.es>
 <1508858729.34364.32.camel@freebsd.org>
To: Ian Lepore <ian@freebsd.org>
X-Mailer: Apple Mail (2.3445.1.7)
X-BeenThere: freebsd-security@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: "Security issues \[members-only posting\]"
 <freebsd-security.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-security>, 
 <mailto:freebsd-security-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-security/>
List-Post: <mailto:freebsd-security@freebsd.org>
List-Help: <mailto:freebsd-security-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-security>, 
 <mailto:freebsd-security-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Oct 2017 15:31:53 -0000



> On 24 Oct 2017, at 17:25, Ian Lepore <ian@freebsd.org> wrote:
>=20
> No, lockf -t 0 means to exit without waiting, with status EX_TEMPFAIL,
> if the lock cannot be acquired immediately.  In light of that, the =
rest
> of your report/request doesn't make sense.  Jobs won't stack up,
> they'll fail if the prior one is still running.

True! Then I don=E2=80=99t understand what happened. When I saw several =
processes waiting I assumed
it was an unlimited wait.=20

My apologies, I need to look into it more closely.




Borja.