Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 03 Jul 2016 09:58:02 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-bugs@FreeBSD.org
Subject:   [Bug 210770] lockf(1): EX_UNAVAILABLE is not returned
Message-ID:  <bug-210770-8@https.bugs.freebsd.org/bugzilla/>

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

            Bug ID: 210770
           Summary: lockf(1): EX_UNAVAILABLE is not returned
           Product: Base System
           Version: 10.1-RELEASE
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: bin
          Assignee: freebsd-bugs@FreeBSD.org
          Reporter: eserte12@yahoo.de

The lockf(1) manpage documents that EX_UNAVAILABLE is returned if -n is used
and the lock file does not exist. This is not the case:

$ lockf -n /tmp/doesnotexist echo; echo $?
lockf: cannot open /tmp/doesnotexist: No such file or directory
73

EX_CANTCREAT (73) is returned instead.

--=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-8>