Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 20 Mar 2019 07:41:14 +0000
From:      bugzilla-noreply@freebsd.org
To:        bugs@FreeBSD.org
Subject:   [Bug 210770] lockf(1): EX_UNAVAILABLE is not returned
Message-ID:  <bug-210770-227-4NSgOSk1uM@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-210770-227@https.bugs.freebsd.org/bugzilla/>
References:  <bug-210770-227@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D210770

--- Comment #1 from commit-hook@freebsd.org ---
A commit references this bug:

Author: avos
Date: Wed Mar 20 07:40:39 UTC 2019
New revision: 345318
URL: https://svnweb.freebsd.org/changeset/base/345318

Log:
  lockf(1): return EX_UNAVAILABLE if -n is used and the lock file does not
  exist

  Apply EX_UNAVAILABLE patch part from PR 170775 to match the documentation.

  Checked with a command from PR 210770:
  lockf -n /tmp/doesnotexist echo; echo $?

  PR:           210770
  MFC after:    1 week

Changes:
  head/usr.bin/lockf/lockf.c

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-210770-227-4NSgOSk1uM>