Descriptipon: Move man-pages to section 8
Author: Sven Hartge <sven@svenhartge.de>
Forwarded: not-needed

--- a/Makefile.am
+++ b/Makefile.am
@@ -46,7 +46,7 @@
 radsecproxy_conf_LDFLAGS = @TARGET_LDFLAGS@
 radsecproxy_hash_LDADD = fticks_hashmac.o hash.o list.o
 
-dist_man_MANS = radsecproxy.1 radsecproxy-hash.1 radsecproxy.conf.5
+dist_man_MANS = radsecproxy.8 radsecproxy-hash.8 radsecproxy.conf.5
 
 EXTRA_DIST = \
 	LICENSE THANKS \
--- a/radsecproxy.1.in
+++ /dev/null
@@ -1,92 +0,0 @@
-.TH radsecproxy 1 "5 July 2018"
-
-.SH "NAME"
-radsecproxy - a generic RADIUS proxy that provides both RADIUS UDP and TCP/TLS (RadSec) transport.
-
-.SH "SYNOPSIS"
-.HP 12
-radsecproxy [\-c \fIconfigfile\fR] [\-d \fIdebuglevel\fR] [\-f] [\-i \fIpidfile\fR] [\-p] [\-v]
-.sp
-
-.SH "DESCRIPTION"
-radsecproxy is a \fBgeneric RADIUS proxy\fR that in addition to to
-usual \fBRADIUS UDP\fR transport, also supports \fBTLS (RadSec)\fR. The
-aim is for the proxy to have sufficient features to be flexible,
-while at the same time to be small, efficient and easy to configure.
-
-The proxy was initially made to be able to deploy \fBRadSec\fR (RADIUS
-over TLS) so that all RADIUS communication across network links
-could be done using TLS, without modifying existing RADIUS software.
-This can be done by running this proxy on the same host as an existing
-RADIUS server or client, and configure the existing client/server to
-talk to localhost (the proxy) rather than other clients and servers
-directly.
-
-There are however other situations where a RADIUS proxy might be
-useful. Some people deploy RADIUS topologies where they want to
-route RADIUS messages to the right server. The nodes that do purely
-routing could be using a proxy. Some people may also wish to deploy
-a proxy on a site boundary. Since the proxy \fBsupports both IPv4
-and IPv6\fR, it could also be used to allow communication in cases
-where some RADIUS nodes use only IPv4 and some only IPv6.
-
-.SH "OPTIONS"
-.TP
-.B \-f
-Run in foreground.
-.br
-By specifying this option, the proxy will run in foreground mode. That
-is, it won't detach. Also all logging will be done to stderr.
-
-.TP
-.B \-d \fIdebuglevel\fR
-This specifies the debug level. It must be set to 1, 2, 3, 4 or 5, where
-1 logs only serious errors, and 5 logs everything. The default is 2 which
-logs errors, warnings and a few informational messages.
-
-.TP
-.B \-p
-Pretend
-.br
-The proxy reads configuration files and performs initialisation as
-usual, but exits prior to creating any sockets. It will return different
-exit codes depending on whether the configuration files are okay. This
-may be used to verify configuration files, and can be done while another
-instance is running.
-
-.TP
-.B \-v
-Print version and exit.
-
-.TP
-.B \-c \fIconfigfile\fR
-This option allows you to specify which config file to use. This is useful
-if you want to use a config file that is not in any of the default locations.
-
-.TP
-.B \-i \fIpidfile\fR
-This option tells the proxy to create a PID file with the specified path.
-
-.SH "SIGNALS"
-The proxy generally exits on all signals. The exceptions are listed below.
-
-.TP
-.B SIGHUP
-.br
-When logging to a file, this signal forces a reopen of the log file.
-.br
-When using TLS or DTLS, reload certificate CRLs.
-
-.TP
-.B SIGPIPE
-.br
-This signal is ignored.
-
-.SH "FILES"
-.TP
-.B @SYSCONFDIR@/radsecproxy.conf
-.sp
-The default configuration file.
-
-.SH "SEE ALSO"
-radsecproxy.conf(5), radsecproxy-hash(1)
--- /dev/null
+++ b/radsecproxy.8.in
@@ -0,0 +1,92 @@
+.TH radsecproxy 8 "5 July 2018"
+
+.SH "NAME"
+radsecproxy - a generic RADIUS proxy that provides both RADIUS UDP and TCP/TLS (RadSec) transport.
+
+.SH "SYNOPSIS"
+.HP 12
+radsecproxy [\-c \fIconfigfile\fR] [\-d \fIdebuglevel\fR] [\-f] [\-i \fIpidfile\fR] [\-p] [\-v]
+.sp
+
+.SH "DESCRIPTION"
+radsecproxy is a \fBgeneric RADIUS proxy\fR that in addition to to
+usual \fBRADIUS UDP\fR transport, also supports \fBTLS (RadSec)\fR. The
+aim is for the proxy to have sufficient features to be flexible,
+while at the same time to be small, efficient and easy to configure.
+
+The proxy was initially made to be able to deploy \fBRadSec\fR (RADIUS
+over TLS) so that all RADIUS communication across network links
+could be done using TLS, without modifying existing RADIUS software.
+This can be done by running this proxy on the same host as an existing
+RADIUS server or client, and configure the existing client/server to
+talk to localhost (the proxy) rather than other clients and servers
+directly.
+
+There are however other situations where a RADIUS proxy might be
+useful. Some people deploy RADIUS topologies where they want to
+route RADIUS messages to the right server. The nodes that do purely
+routing could be using a proxy. Some people may also wish to deploy
+a proxy on a site boundary. Since the proxy \fBsupports both IPv4
+and IPv6\fR, it could also be used to allow communication in cases
+where some RADIUS nodes use only IPv4 and some only IPv6.
+
+.SH "OPTIONS"
+.TP
+.B \-f
+Run in foreground.
+.br
+By specifying this option, the proxy will run in foreground mode. That
+is, it won't detach. Also all logging will be done to stderr.
+
+.TP
+.B \-d \fIdebuglevel\fR
+This specifies the debug level. It must be set to 1, 2, 3, 4 or 5, where
+1 logs only serious errors, and 5 logs everything. The default is 2 which
+logs errors, warnings and a few informational messages.
+
+.TP
+.B \-p
+Pretend
+.br
+The proxy reads configuration files and performs initialisation as
+usual, but exits prior to creating any sockets. It will return different
+exit codes depending on whether the configuration files are okay. This
+may be used to verify configuration files, and can be done while another
+instance is running.
+
+.TP
+.B \-v
+Print version and exit.
+
+.TP
+.B \-c \fIconfigfile\fR
+This option allows you to specify which config file to use. This is useful
+if you want to use a config file that is not in any of the default locations.
+
+.TP
+.B \-i \fIpidfile\fR
+This option tells the proxy to create a PID file with the specified path.
+
+.SH "SIGNALS"
+The proxy generally exits on all signals. The exceptions are listed below.
+
+.TP
+.B SIGHUP
+.br
+When logging to a file, this signal forces a reopen of the log file.
+.br
+When using TLS or DTLS, reload certificate CRLs.
+
+.TP
+.B SIGPIPE
+.br
+This signal is ignored.
+
+.SH "FILES"
+.TP
+.B @SYSCONFDIR@/radsecproxy.conf
+.sp
+The default configuration file.
+
+.SH "SEE ALSO"
+radsecproxy.conf(5), radsecproxy-hash(8)
--- a/radsecproxy-hash.1
+++ /dev/null
@@ -1,29 +0,0 @@
-.TH radsecproxy-hash 1 "5 May 2018"
-
-.SH "NAME"
-radsecproxy-hash - print digests of Ethernet MAC addresses
-
-.SH "SYNOPSIS"
-.HP 12
-radsecproxy-hash [\-h] [\-k \fIKEY\fR] [\fIMAC\fR...]
-.sp
-
-.SH "DESCRIPTION"
-Print the hash or hmac of Ethernet \fIMAC\fR addresses
-
-.SH "OPTIONS"
-.TP
-.B \-h
-Display help and exit
-
-.TP
-.B \-k \fIKEY\fR
-.br
-perform HMAC calculation using key \fIKEY\fR
-
-.TP
-With no \fIMAC\fR, read from standard input
-
-
-.SH "SEE ALSO"
-radsecproxy.conf(5)
--- /dev/null
+++ b/radsecproxy-hash.8
@@ -0,0 +1,29 @@
+.TH radsecproxy-hash 8 "5 May 2018"
+
+.SH "NAME"
+radsecproxy-hash - print digests of Ethernet MAC addresses
+
+.SH "SYNOPSIS"
+.HP 12
+radsecproxy-hash [\-h] [\-k \fIKEY\fR] [\fIMAC\fR...]
+.sp
+
+.SH "DESCRIPTION"
+Print the hash or hmac of Ethernet \fIMAC\fR addresses
+
+.SH "OPTIONS"
+.TP
+.B \-h
+Display help and exit
+
+.TP
+.B \-k \fIKEY\fR
+.br
+perform HMAC calculation using key \fIKEY\fR
+
+.TP
+With no \fIMAC\fR, read from standard input
+
+
+.SH "SEE ALSO"
+radsecproxy.conf(5)
--- a/configure.ac
+++ b/configure.ac
@@ -93,7 +93,7 @@
 fi
 
 dnl Substitute variables such as sysconfdir
-AC_CONFIG_FILES([radsecproxy.1 radsecproxy.conf.5])
+AC_CONFIG_FILES([radsecproxy.8 radsecproxy.conf.5])
 
 dnl Expand sysconfdir early to avoid two layers of substitution
 test "x$prefix" = xNONE && prefix=$ac_default_prefix
