>Number:         13168
>Category:       admin
>Synopsis:       shlock(1) mentions an option -v which doesn't actually exist
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    netbsd-admin
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Jun 11 02:06:00 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     Masao Uebayashi
>Release:        1.5.1_BETA
>Organization:
SOUM Corporation, Japan.
>Environment:
NetBSD satoko.soum.co.jp 1.5.1_BETA NetBSD 1.5.1_BETA (SATOKO) #1: Fri May 11 18:35:05 JST 2001     root@satoko.soum.co.jp:/usr/src/sys/arch/i386/compile/SATOKO i386
>Description:

>How-To-Repeat:
Type 'shlock -f /tmp/foo -v'
>Fix:
diff -u usr.bin/shlock/shlock.1.orig usr.bin/shlock/shlock.1
--- usr.bin/shlock/shlock.1.orig        Wed May 23 18:20:29 2001
+++ usr.bin/shlock/shlock.1     Mon Jun 11 18:08:13 2001
@@ -10,9 +10,9 @@
 .Nm
 .Fl f
 .Ar lockfile
+.Op Fl d
 .Op Fl p Ar PID
 .Op Fl u
-.Op Fl v
 .Sh DESCRIPTION
 The
 .Nm
@@ -52,6 +52,12 @@
 is always required.
 .Pp
 The
+.Fl d
+option causes
+.Nm
+to print debug messages about what it is doing.
+.Pp
+The
 .Fl p
 option with
 .Ar PID
@@ -65,12 +71,6 @@
 .Nm
 to read and write the PID as a binary pid_t, instead of as ASCII,
 to be compatible with the locks created by UUCP.
-.Pp
-The
-.Fl v
-option causes
-.Nm
-to be verbose about what it is doing.
 .Sh RETURN VALUES
 A zero exit code indicates a valid lock file.
 .Sh EXAMPLES


>Release-Note:
>Audit-Trail:
>Unformatted: