tags 295568 + patch
thanks

Hello,

Here is a patch that fixes this problem.

Regards,

Kapil.

# Fix the hyphens used as minus sign error in the manpages.

Index: tsocks-1.8/debian/plus/tsocks.1
===================================================================
--- tsocks-1.8.orig/debian/plus/tsocks.1        2006-10-28 16:16:26.000000000 
+0530
+++ tsocks-1.8/debian/plus/tsocks.1     2006-10-28 15:49:59.000000000 +0530
@@ -10,7 +10,7 @@
 .br
 or
 .B tsocks
-.RB [-on|-off]
+.RB [\-on|\-off]
 .br
 or
 .B tsocks
@@ -23,7 +23,7 @@
 run the application as specified with the environment (LD_PRELOAD) set
 such that tsocks(8) will transparently proxy SOCKS connections in 
 that program
-.IP \fB[-on|-off]
+.IP \fB[\-on|\-off]
 this option adds or removes tsocks(8) from the LD_PRELOAD environment
 variable. When tsocks(8) is in this variable all executed
 applications are automatically socksified. If you want to
@@ -32,12 +32,12 @@
 .br
 Example:
 .br
-". tsocks -on" -- add the tsocks lib to LD_PRELOAD (don't forget the
+". tsocks \-on" \-\- add the tsocks lib to LD_PRELOAD (don't forget the
 leading dot!)
 .br
-". tsocks -off" -- remove the tsocks lib from LD_PRELOAD (don't forget the
+". tsocks \-off" \-\- remove the tsocks lib from LD_PRELOAD (don't forget the
 leading dot!)
-.IP \fB[-show|-sh]
+.IP \fB[\-show|\-sh]
 show the current value of the LD_PRELOAD variable
 .IP \fB<without\ any\ argument>
 create a new shell with LD_PRELOAD including tsocks(8). 
Index: tsocks-1.8/tsocks.8
===================================================================
--- tsocks-1.8.orig/tsocks.8    2006-10-28 16:25:59.000000000 +0530
+++ tsocks-1.8/tsocks.8 2006-10-28 15:49:59.000000000 +0530
@@ -13,11 +13,11 @@
 The syntax to force preload of the library for different shells is
 specified below:
  
-Bash, Ksh and Bourne shell -
+Bash, Ksh and Bourne shell \-
 
 export LD_PRELOAD=/lib/libtsocks.so
 
-C Shell - 
+C Shell \-
 
 setenv LD_PRELOAD=/lib/libtsocks.so
 
@@ -52,18 +52,18 @@
 Most arguments to
 .BR tsocks
 are provided in the configuration file (the location of which is defined
-at configure time by the --with-conf=<file> argument but defaults to
+at configure time by the \-\-with\-conf=<file> argument but defaults to
 /etc/tsocks.conf). The structure of this file is documented in tsocks.conf(8)
 
 Some configuration options can be specified at run time using environment
 variables as follows: 
 
 .TP
-.I TSOCKS_CONFFILE
+.I TSOCKS_CONF_FILE
 This environment variable overrides the default location of the tsocks 
 configuration file. This variable is not honored if the program tsocks
 is embedded in is setuid. In addition this environment variable can
-be compiled out of tsocks with the --disable-envconf argument to 
+be compiled out of tsocks with the \-\-disable\-envconf argument to
 configure at build time
 
 .TP
@@ -73,10 +73,10 @@
 standard error). If this variable is not present by default the logging 
 level is set to 0 which indicates that only error messages should be output. 
 Setting it to higher values will cause tsocks to generate more messages 
-describing what it is doing. If set to -1 tsocks will output absolutely no 
+describing what it is doing. If set to \-1 tsocks will output absolutely no
 error or debugging messages. This is only needed if tsocks output interferes 
 with a program it is embedded in. Message output can be permanently compiled 
-out of tsocks by specifying the --disable-debug option to configure at 
+out of tsocks by specifying the \-\-disable\-debug option to configure at
 build time
 
 .TP
@@ -85,7 +85,7 @@
 be sent to standard error) to a file. This variable is not honored if the 
 program tsocks is embedded in is setuid. For programs where tsocks output 
 interferes with normal operation this option is generally better than 
-disabling messages (with TSOCKS_DEBUG = -1)
+disabling messages (with TSOCKS_DEBUG = \-1)
 
 .TP
 .I TSOCKS_USERNAME
@@ -115,8 +115,8 @@
 .BR tsocks
 will generate error messages and print them to stderr when there are
 problems with the configuration file or the SOCKS negotiation with the
-server if the TSOCKS_DEBUG environment variable is not set to -1 or and
---disable-debug was not specified at compile time. This output may cause
+server if the TSOCKS_DEBUG environment variable is not set to \-1 or and
+\-\-disable\-debug was not specified at compile time. This output may cause
 some problems with programs that redirect standard error.
 
 .SS CAVEATS
@@ -162,7 +162,7 @@
 through the syscall() routine.
 
 .SH FILES
-/etc/tsocks.conf - default tsocks configuration file
+/etc/tsocks.conf \- default tsocks configuration file
 
 .SH SEE ALSO
 tsocks.conf(5)
Index: tsocks-1.8/tsocks.conf.5
===================================================================
--- tsocks-1.8.orig/tsocks.conf.5       2006-10-28 16:25:59.000000000 +0530
+++ tsocks-1.8/tsocks.conf.5    2006-10-28 15:49:59.000000000 +0530
@@ -66,7 +66,7 @@
 .I server
 The IP address of the SOCKS server (e.g "server = 10.1.4.253"). Only one
 server may be specified per path block, or one outside a path
-block (to define the default server). Unless --disable-hostnames was 
+block (to define the default server). Unless \-\-disable\-hostnames was
 specified to configure at compile time the server can be specified as 
 a hostname (e.g "server = socks.nec.com") 
 
@@ -118,13 +118,13 @@
 .TP
 .I reaches
 This directive is only valid inside a path block. Its parameter is formed
-as IP[:startport[-endport]]/Subnet and it specifies a network (and a range
+as IP[:startport[\-endport]]/Subnet and it specifies a network (and a range
 of ports on that network) that can be accessed by the SOCKS server specified
 in this path block. For example, in a path block "reaches =
-150.0.0.0:80-1024/255.0.0.0" indicates to tsocks that the SOCKS server 
+150.0.0.0:80\-1024/255.0.0.0" indicates to tsocks that the SOCKS server
 specified in the current path block should be used to access any IPs in the 
 range 150.0.0.0 to 150.255.255.255 when the connection request is for ports
-80-1024.
+80\-1024.
 
 .SH UTILITIES
 tsocks comes with two utilities that can be useful in creating and verifying
@@ -146,12 +146,12 @@
 extremely useful in debugging problems.
 
 validateconf can read a configuration file from a location other than the 
-location specified at compile time with the -f <filename> command line 
+location specified at compile time with the \-f <filename> command line
 option.
 
 Normally validateconf simply dumps the configuration read to the screen (in
 a nicely readable format), however it also has a useful 'test' mode. When
-passed a hostname/ip on the command line like -t <hostname/ip>, validateconf 
+passed a hostname/ip on the command line like \-t <hostname/ip>, validateconf
 determines which of the SOCKS servers specified in the configuration file 
 would be used by tsocks to access the specified host. 
 
--

Attachment: signature.asc
Description: Digital signature

Reply via email to