Simplify locking description: most things have nice default values these

days, the casual user doesn't need more than defining LOCKDIR to get
locks working on the ports tree.

1 files changed, 10 insertions, 7 deletions

diff --git a/share/man/man7/ports.7 b/share/man/man7/ports.7
index d33191fe511..cd00cfdea40 100644
--- a/share/man/man7/ports.7
+++ b/share/man/man7/ports.7
@@ -23,10 +23,10 @@
 .\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
 .\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 .\"
-.\" $OpenBSD: ports.7,v 1.69 2007/05/31 19:19:58 jmc Exp $
+.\" $OpenBSD: ports.7,v 1.70 2007/08/15 14:20:54 espie Exp $
 .\" $FreeBSD: ports.7,v 1.7 1998/06/23 04:38:50 hoek Exp $
 .\"
-.Dd $Mdocdate: May 31 2007 $
+.Dd $Mdocdate: August 15 2007 $
 .Dt PORTS 7
 .Os
 .Sh NAME
@@ -326,11 +326,8 @@ The ports tree can be used concurrently for building several ports at the
 same time, thanks to a locking mechanism.
 By default, this mechanism is disabled.
 Defining
-.Ev LOCKDIR ,
-.Ev LOCK_CMD ,
-and
-.Ev UNLOCK_CMD
-to proper values will activate it.
+.Ev LOCKDIR 
+to a proper value will activate it.
 .Pp
 All locks will be stored in
 .Pa ${LOCKDIR} .
@@ -342,6 +339,12 @@ should be used to release it.
 Locks are named ${LOCKDIR}/${FULLPKGNAME}.lock,
 or ${LOCKDIR}/${DISTFILE}.lock for distfiles fetching.
 .Pp
+The default values of
+.Ev LOCK_CMD
+and
+.Ev UNLOCK_CMD
+are appropriate for most uses.
+.Pp
 The locking protocol follows a big-lock model: each top-level target
 in a port directory will acquire the corresponding lock, complete its job,
 then release the lock, e.g., running