lock directory -> locks directory

ok espie@
This commit is contained in:
rpe 2012-10-26 14:43:17 +00:00
parent 1c1cada0da
commit 92c015487d

View File

@ -1,4 +1,4 @@
.\" $OpenBSD: dpb.1,v 1.46 2012/10/13 09:10:07 espie Exp $
.\" $OpenBSD: dpb.1,v 1.47 2012/10/26 14:43:17 rpe Exp $
.\"
.\" Copyright (c) 2010 Marc Espie <espie@openbsd.org>
.\"
@ -14,7 +14,7 @@
.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
.\"
.Dd $Mdocdate: October 13 2012 $
.Dd $Mdocdate: October 26 2012 $
.Dt DPB 1
.Os
.Sh NAME
@ -535,7 +535,7 @@ since distfiles are checksummed after the fetch anyways.
.Sh LOCKS AND ERRORS
When building a package,
.Nm
produces a lockfile in the lock directory, whose name is deduced from
produces a lockfile in the locks directory, whose name is deduced from
the basic pkgpath with slashes replaced by dots.
This lockfile is filled with such info as the build start time or the host,
or the needed dependencies for this pkgpath.
@ -559,7 +559,7 @@ Normal list of tasks is:
.Pp
At the end of each job,
.Nm
rechecks the lock directory for existing lockfiles.
rechecks the locks directory for existing lockfiles.
If some locks have vanished,
it will put the corresponding paths back in the queue and attempt
another build.