[lockdev-devel] [PATCH 07/10] RedHat patch 7
Ludwig Nussel
ludwig.nussel at suse.de
Wed Feb 10 11:45:37 UTC 2010
- add man page
---
Makefile | 2 ++
docs/lockdev.8 | 45 +++++++++++++++++++++++++++++++++++++++++++++
2 files changed, 47 insertions(+), 0 deletions(-)
create mode 100644 docs/lockdev.8
diff --git a/Makefile b/Makefile
index 3b351dd..cddeaca 100644
--- a/Makefile
+++ b/Makefile
@@ -71,7 +71,9 @@ install_profile: ${static} ${shared}
install_doc: docs/lockdev.3
install -m755 -d ${mandir}/man3
+ install -m755 -d ${mandir}/man8
install -m644 docs/lockdev.3 ${mandir}/man3
+ install -m644 docs/lockdev.8 ${mandir}/man8
install_run: ${shared}
install -m755 -d ${libdir}
diff --git a/docs/lockdev.8 b/docs/lockdev.8
new file mode 100644
index 0000000..f2cd8d2
--- /dev/null
+++ b/docs/lockdev.8
@@ -0,0 +1,45 @@
+.\"
+.TH LOCKDEV 8 "SEPTEMBER 2009" "" ""
+.\"
+.\" Man page written by Jiri Popelka <jpopelka AT redhat DOT com>
+.\"
+.SH NAME
+\fBLockdev\fR is a setgid binary,
+which provides a reliable way to put an exclusive lock
+in /var/lock to devices (e.g. ttyS0) using both FSSTND and SVr4 methods,
+so regular users don't need write access there.
+
+This task is achieved through calls to the liblockdev(3) API.
+
+.SH SYNOPSIS
+.B /usr/sbin/lockdev
+.RB [< operation >]
+.RB < device >
+
+.SH DESCRIPTION
+The \fBlockdev\fR command can perform one of the following operations (calls to liblockdev(3) API):
+
+\fB-l\fR - lock device with \fBdev_lock()\fR function
+
+\fB-u\fR - unlock device with \fBdev_unlock()\fR function
+
+\fBno operation\fR - test lock with \fBdev_testlock()\fR function
+
+.SH RETURN VALUES
+ Value dev_lock dev_unlock dev_testlock
+ 0 OK OK not locked
+ 1 locked other locked other locked
+ 2 EACCES
+ 3 EROFS
+ 4 EFAULT
+ 5 EINVAL
+ 6 ENAMETOOLONG
+ 7 ENOENT
+ 8 ENOTDIR
+ 9 ENOMEM
+ 10 ELOOP
+ 11 EIO
+ 255 error error error
+
+.SH SEE ALSO
+.BR lockdev (3).
--
1.6.4.2
More information about the lockdev-devel
mailing list