File: 05-Manpages.patch

package info (click to toggle)
super 3.30.1-1
  • links: PTS, VCS
  • area: main
  • in suites: buster
  • size: 1,860 kB
  • sloc: ansic: 24,673; sh: 297; makefile: 296
file content (127 lines) | stat: -rw-r--r-- 3,631 bytes parent folder | download | duplicates (3)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
From: Robert Luberda <robert@debian.org>
Date: Sat, 19 Apr 2008 17:25:00 +0200
Subject: 05 Manpages.

Man pages fixes.
---
 super.1.in | 13 ++++++-------
 super.5.in | 14 +++++++-------
 2 files changed, 13 insertions(+), 14 deletions(-)

diff --git a/super.1.in b/super.1.in
index 0d38f6e..888c739 100644
--- a/super.1.in
+++ b/super.1.in
@@ -311,8 +311,7 @@ you can instead start the .supertab file with:
 .nf
 #! /bin/sh
 # Keep this backslash -> \\
-	exec /long/path/to/the/super/executable -o $0 ${1+"$@"}
-...
+	exec /long/path/to/the/super/executable \-o $0 ${1+"$@"}
 .fi
 .RE
 (The above takes advantage of the fact that super allows comments to
@@ -321,7 +320,7 @@ be backslash-continued, but the shell doesn't.)
 Per-user .supertab linking works as follows: if
 .I /path/to/xyz
 is a symlink to some user's .supertab file, and the .supertab file
-begins with \fI#! /path/to/super -o\fP,
+begins with \fI#! /path/to/super \-o\fP,
 then the shell will invoke
 .I super
 with arguments something like
@@ -472,9 +471,9 @@ that \fIsuper foo\fP is a valid command:
 .in +.5i
 .nf
 prog=\`basename $0\`
-/usr/local/bin/super -t -r $0 $prog
+/usr/local/bin/super \-t \-r $0 $prog
 case $? in
-0 ) exec /usr/local/bin/super -t -r $0 $prog ;;
+0 ) exec /usr/local/bin/super \-t \-r $0 $prog ;;
 * ) echo "Super $prog doesn't work!"
     ... So take appropriate action ...
     ;;
@@ -656,7 +655,7 @@ itself by beginning the script in the following way:
 #!/bin/sh
 prog=\`basename $0\`
 test "X$SUPERCMD" = "X$prog" ||
-		exec /usr/local/bin/super -r $0 $prog ${1+"$@"}
+		exec /usr/local/bin/super \-r $0 $prog ${1+"$@"}
 .fi
 .in -.5i
 Here, the path that is exec'd should be replaced with the
@@ -689,7 +688,7 @@ into the
 .I super.tab
 file.
 .SH "SEE ALSO"
-.BR super (5).
+.BR super.tab (5).
 .SH AUTHOR
 Will Deich
 .br
diff --git a/super.5.in b/super.5.in
index 869c77d..9c9ca85 100644
--- a/super.5.in
+++ b/super.5.in
@@ -1,4 +1,4 @@
-.TH SUPER 5 local
+.TH SUPER.TAB 5 local
 .\"
 .\"	Copyright (c) 1993 by California Institute of Technology.
 .\"	Written by William Deich.  Not derived from licensed software.
@@ -8,7 +8,7 @@
 .\"  
 .\"
 .SH NAME
-super, super.tab \- database of restricted commands for super(1)
+super.tab \- database of restricted commands for super(1)
 .SH DESCRIPTION
 The
 .I super.tab
@@ -88,7 +88,7 @@ using effective uid root; unchanged real uid and gid;
 no supplementary groups; no open file descriptors save 0, 1, and 2;
 no environment variables except a few with safe values
 (see 
-.BR super.1 );
+.BR super (1));
 and signal handling reset to the default.
 .PP
 When
@@ -1551,7 +1551,7 @@ and
 .B syslog
 options.
 For instance,
-\fImail="mail -s Super joeblow"\fR
+\fImail="mail \-s Super joeblow"\fR
 will cause error messages to be mailed to user
 .I joeblow
 (on some systems you may need to substitute
@@ -1641,7 +1641,7 @@ Super doesn't know what are sensible codes \(em it's up to the
 .I super.tab
 writer to choose meaningful values.  For instance, if you put
 .ti +.5i
-.B\ syslog_error="LOG_INFO\ |\ LOG_ERR"\ \fI(bad!)\fP
+.B syslog_error="LOG_INFO\ |\ LOG_ERR"\ \fI(bad!)\fP
 .br
 then you will get both those values or'd together and passed to
 .I syslog().
@@ -1776,7 +1776,7 @@ The
 can be
 .B password
 or
-.B PAM
+.B pam
 (if PAM is supported on your system).
 The default is
 .BR password .
@@ -2027,7 +2027,7 @@ For example, suppose you want to permit users to safely mount zip disks,
 and you use something like:
 .ti +.5i
 .B zipmount
-"/etc/mount -o nosuid /dev/xz10  /zip"
+"/etc/mount \-o nosuid /dev/xz10  /zip"
 .br
 This command will fail if
 .I /etc/mount