docs/man/*: fix man page section assignments for end-user interactive clients (man1) [networkupstools#2977]

* Section 1 (programs): upsc, upscmd, upsrw, NUT-Monitor
* Section 8 (daemons): upsmon, upssched

Signed-off-by: Jim Klimov <[email protected]>

Author: jimklimov

docs/config-notes.txt

@@ -421,7 +421,7 @@ probably misconfigured during the <<Driver_configuration, Driver configuration>>
 step.  If you reconfigure the driver, use `upsdrvctl stop` to stop it, then
 start it again as shown in the <<Starting_drivers, Starting driver(s)>> step.
 
-Reference: man page: linkman:upsc[8]
+Reference: man page: linkman:upsc[1]
 
 
 All data
@@ -481,7 +481,7 @@ above.  A sample run on an UPS (Eaton Ellipse MAX 1100) looks like this:
 	ups.timer.start: -1
 	ups.vendorid: 0463
 
-Reference: man page: linkman:upsc[8],
+Reference: man page: linkman:upsc[1],
 <<nut-names,NUT command and variable naming scheme>>
 
 Startup scripts

docs/man/Makefile.am

@@ -334,13 +334,13 @@ SRC_CLIENT_PAGES = \
 
 INST_MAN_CLIENT_PAGES = \
 	nutupsdrv.$(MAN_SECTION_CMD_SYS) \
-	upsc.$(MAN_SECTION_CMD_SYS) \
-	upscmd.$(MAN_SECTION_CMD_SYS) \
+	upsc.$(MAN_SECTION_CMD_USR) \
+	upscmd.$(MAN_SECTION_CMD_USR) \
 	upsd.$(MAN_SECTION_CMD_SYS) \
 	upsdrvctl.$(MAN_SECTION_CMD_SYS) \
 	upslog.$(MAN_SECTION_CMD_SYS) \
 	upsmon.$(MAN_SECTION_CMD_SYS) \
-	upsrw.$(MAN_SECTION_CMD_SYS) \
+	upsrw.$(MAN_SECTION_CMD_USR) \
 	upssched.$(MAN_SECTION_CMD_SYS)
 
 INST_HTML_CLIENT_MANS = \
@@ -399,19 +399,19 @@ DIST_ALL_MAN_PAGES += $(MAN_CLIENT_PAGES_ADDON_NUT_EXE)
 endif !HAVE_WINDOWS
 
 MAN_CLIENT_PAGES_ADDON_NUT_MONITOR = \
-	NUT-Monitor-py2gtk2.$(MAN_SECTION_CMD_SYS) \
-	NUT-Monitor-py3qt5.$(MAN_SECTION_CMD_SYS) \
-	NUT-Monitor-py3qt6.$(MAN_SECTION_CMD_SYS) \
-	NUT-Monitor.$(MAN_SECTION_CMD_SYS)
+	NUT-Monitor-py2gtk2.$(MAN_SECTION_CMD_USR) \
+	NUT-Monitor-py3qt5.$(MAN_SECTION_CMD_USR) \
+	NUT-Monitor-py3qt6.$(MAN_SECTION_CMD_USR) \
+	NUT-Monitor.$(MAN_SECTION_CMD_USR)
 
 # Alias page for one text describing two commands:
-NUT-Monitor-py2gtk2.$(MAN_SECTION_CMD_SYS): NUT-Monitor.$(MAN_SECTION_CMD_SYS)
+NUT-Monitor-py2gtk2.$(MAN_SECTION_CMD_USR): NUT-Monitor.$(MAN_SECTION_CMD_USR)
 	touch $@
 
-NUT-Monitor-py3qt5.$(MAN_SECTION_CMD_SYS): NUT-Monitor.$(MAN_SECTION_CMD_SYS)
+NUT-Monitor-py3qt5.$(MAN_SECTION_CMD_USR): NUT-Monitor.$(MAN_SECTION_CMD_USR)
 	touch $@
 
-NUT-Monitor-py3qt6.$(MAN_SECTION_CMD_SYS): NUT-Monitor.$(MAN_SECTION_CMD_SYS)
+NUT-Monitor-py3qt6.$(MAN_SECTION_CMD_USR): NUT-Monitor.$(MAN_SECTION_CMD_USR)
 	touch $@
 
 if WITH_NUT_MONITOR

docs/man/NUT-Monitor.txt

@@ -1,4 +1,4 @@
-NUT-Monitor(8)
+NUT-Monitor(1)
 ==============
 
 NAME
@@ -47,9 +47,9 @@ actual Python UI client.
 
 For each individual run, the UI client can connect to a single NUT data server
 and a device on it.  This can use either anonymous read-only connections (like
-linkman:upsc[8]), or authenticated connections (see linkman:upsd.users[5])
-which can also issue commands to the driver (like linkman:upscmd[8]) and
-set supported variables (like linkman:upsrw[8]) -- propagated to the device,
+linkman:upsc[1]), or authenticated connections (see linkman:upsd.users[5])
+which can also issue commands to the driver (like linkman:upscmd[1]) and
+set supported variables (like linkman:upsrw[1]) -- propagated to the device,
 where applicable.
 
 The Python UI client can be used on a system different from the NUT data
@@ -96,9 +96,9 @@ AUTHORS
 SEE ALSO
 --------
 
-linkman:upsc[8],
-linkman:upscmd[8],
-linkman:upsrw[8],
+linkman:upsc[1],
+linkman:upscmd[1],
+linkman:upsrw[1],
 linkman:upsd.users[5]
 
 Internet resources:

docs/man/al175.txt

@@ -40,7 +40,7 @@ linkman:ups.conf[5].
 INSTANT COMMANDS
 ----------------
 
-This driver supports some extra commands (see linkman:upscmd[8]):
+This driver supports some extra commands (see linkman:upscmd[1]):
 
 *test.battery.start*::
 Start a battery test.

docs/man/bicker_ser.txt

@@ -38,7 +38,7 @@ VARIABLES
 ---------
 
 Depending on the type of your UPS unit, some of the following variables may
-be changed with linkman:upsrw[8]. If the driver can't read a variable from the
+be changed with linkman:upsrw[1]. If the driver can't read a variable from the
 UPS, it will not be made available. Whenever not explicitly stated, any variable
 can be disabled, in which case the action it performs will not be executed. To
 disable a variable, set it to an empty value.

docs/man/blazer-common.txt

@@ -156,7 +156,7 @@ endif::blazer_usb[]
 UPS COMMANDS
 ------------
 
-This driver supports some instant commands (see linkman:upscmd[8]):
+This driver supports some instant commands (see linkman:upscmd[1]):
 
 *beeper.toggle*::
 
@@ -305,7 +305,8 @@ endif::blazer_usb[]
 ifndef::blazer_usb[]
 linkman:blazer_usb[8],
 endif::blazer_usb[]
-linkman:nutupsdrv[8], linkman:upsc[8], linkman:upscmd[8], linkman:upsrw[8]
+linkman:nutupsdrv[8],
+linkman:upsc[1], linkman:upscmd[1], linkman:upsrw[1]
 
 
 Internet Resources:

docs/man/clone-outlet.txt

@@ -179,8 +179,8 @@ Arjen de Korte <[email protected]>
 SEE ALSO
 --------
 
-linkman:upscmd[8],
-linkman:upsrw[8],
+linkman:upscmd[1],
+linkman:upsrw[1],
 linkman:ups.conf[5],
 linkman:clone[8],
 linkman:nutupsdrv[8]

docs/man/clone.txt

@@ -216,8 +216,8 @@ Arjen de Korte <[email protected]>
 SEE ALSO
 --------
 
-linkman:upscmd[8],
-linkman:upsrw[8],
+linkman:upscmd[1],
+linkman:upsrw[1],
 linkman:ups.conf[5],
 linkman:clone-outlet[8],
 linkman:nutupsdrv[8]

docs/man/dummy-ups.txt

@@ -33,8 +33,8 @@ Dummy Mode
 In this mode, *dummy-ups* looks like a standard NUT device driver to
 linkman:upsd[8] and allows one to change any value for testing purposes.
 
-It is both interactive, controllable through the linkman:upsrw[8] and
-linkman:upscmd[8] commands (or equivalent graphical tool), and batchable
+It is both interactive, controllable through the linkman:upsrw[1] and
+linkman:upscmd[1] commands (or equivalent graphical tool), and batchable
 through script files.
 
 It can be configured, launched and used as any other "real" NUT driver.
@@ -141,7 +141,7 @@ This definition file, specified by the `port` argument in the example above,
 is generally named `something.dev` or `something.seq`. It contains a list of
 all valid variables and associated values (you can later use `upsrw`
 only to modify values of these variables), and has the same format as an
-linkman:upsc[8] data dump (`<varname>: <value>`). This means you can easily
+linkman:upsc[1] data dump (`<varname>: <value>`). This means you can easily
 create definition files from an existing UPS using `upsc > file.dev`.
 
 Note that the Network UPS project provides an extensive
@@ -250,7 +250,7 @@ INTERACTION
 Once the driver is loaded in dummy mode, you can change any variables, except
 those of the `driver.*` and `server.*` collections.
 You can do this by either editing the definition file, or use the
-linkman:upsrw[8] and linkman:upscmd[8] commands.
+linkman:upsrw[1] and linkman:upscmd[1] commands.
 
 Note that in simulation mode, new variables can be added on the fly, but only
 by adding these to the definition file (and waiting for it to be re-read).
@@ -315,8 +315,8 @@ Arnaud Quette
 SEE ALSO
 --------
 
-linkman:upscmd[8],
-linkman:upsrw[8],
+linkman:upscmd[1],
+linkman:upsrw[1],
 linkman:ups.conf[5],
 linkman:nutupsdrv[8]
 

docs/man/failover.txt

@@ -27,7 +27,7 @@ for "primary" duty according to a set of user configurable rules and priorities.
 At any given time, `failover` designates one UPS driver as the *primary*, and
 presents its commands, variables and status to the outside world as if it were
 directly talking to that UPS. From the perspective of the clients (such as
-linkman:upsmon[8] or linkman:upsc[8]), the `failover` driver behaves like any
+linkman:upsmon[8] or linkman:upsc[1]), the `failover` driver behaves like any
 single UPS, abstracting away the underlying redundancy, and allowing for
 seamless transitioning between all monitored UPS drivers and their datasets.
 
@@ -183,7 +183,7 @@ Any linkman:upsmon[8] clients would be set to monitor the `failover` UPS.
 
 The driver fully supports setting variables and performing instant commands on
 the currently elected primary UPS driver, which are proxied and with end-to-end
-tracking also being possible (linkman:upscmd[8] and linkman:upsrw[8] `-w`). You
+tracking also being possible (linkman:upscmd[1] and linkman:upsrw[1] `-w`). You
 may notice some variables and commands will be prefixed with `upstream.`, this
 is to clearly separate the upstream commands from those of `failover` itself.
 
@@ -281,10 +281,10 @@ Sebastian Kuttnig <[email protected]>
 SEE ALSO
 --------
 
-linkman:upscmd[8],
-linkman:upsrw[8],
+linkman:upscmd[1],
+linkman:upsrw[1],
 linkman:ups.conf[5],
-linkman:upsc[8],
+linkman:upsc[1],
 linkman:upsmon[8],
 linkman:nutupsdrv[8],
 linkman:clone[8],

docs/man/genericups.txt

@@ -284,7 +284,7 @@ Start the driver with the type you want to try, e.g.:
 
         genericups -x upstype=n /dev/port
 
-Let linkman:upsd[8] sync up (watch the syslog), and then run linkman:upsc[8]
+Let linkman:upsd[8] sync up (watch the syslog), and then run linkman:upsc[1]
 to see what it found.  If the `STATUS` is correct (should be "OL" for online),
 continue to <<_step_3,Step 3>>, otherwise go back to step 1.
 

docs/man/huawei-ups2000.txt

@@ -197,7 +197,7 @@ as line power is restored.
 INSTANT COMMANDS
 ----------------
 
-This driver supports some instant commands (see linkman:upscmd[8]):
+This driver supports some instant commands (see linkman:upscmd[1]):
 
 *shutdown.stayoff*::
 After an *offdelay*, turn off the load. When line power is back,
@@ -277,7 +277,7 @@ Stop a running battery test.
 VARIABLES
 ---------
 
-This driver supports some writable runtime variables (see linkman:upsrw[8]):
+This driver supports some writable runtime variables (see linkman:upsrw[1]):
 
 **ups.beeper.status**::
 Enable or disable the UPS beeper, *disabled* or *enabled*.

docs/man/index.txt

@@ -30,21 +30,21 @@ Configuration files
 - linkman:upsset.conf[5]
 - linkman:upsstats.html[5]
 
-Daemons
-~~~~~~~
+Server and Client Daemons
+~~~~~~~~~~~~~~~~~~~~~~~~~
 
 - linkman:upsd[8]
 - linkman:upsmon[8]
 - linkman:upssched[8]
 - linkman:upslog[8]
 
-Clients commands
-~~~~~~~~~~~~~~~~
+End-User Clients and Commands
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-- linkman:upsc[8]
-- linkman:upscmd[8]
-- linkman:upsrw[8]
-- linkman:NUT-Monitor[8]
+- linkman:upsc[1]
+- linkman:upscmd[1]
+- linkman:upsrw[1]
+- linkman:NUT-Monitor[1]
 
 Configuration commands
 ~~~~~~~~~~~~~~~~~~~~~~

docs/man/nut.txt

@@ -148,10 +148,10 @@ The "primary" system is usually also responsible for commanding the managed
   and reboots them) just because external power returned when the shut down
   spree had already started.
 
-* linkman:upsc[8] is a command-line client for anonymous read-only access,
+* linkman:upsc[1] is a command-line client for anonymous read-only access,
   used to list devices served by a NUT data server, or to query data points
   reported by a particular device.
-* linkman:NUT-Monitor[8] is a GUI client for read-only or read-write access.
+* linkman:NUT-Monitor[1] is a GUI client for read-only or read-write access.
 * A suite of CGI clients can run on a web server like Apache or nginx to
   provide a simple HTML interface to your devices.
 
@@ -309,7 +309,7 @@ into certain directories according to their documentation:
 linkman:hosts.conf[5] and linkman:upsset.conf[5] for configuration,
 and `upsstats-single.html` and `upsstats.html` for HTML UI templates.
 
-Other clients, whether delivered by NUT project (linkman:NUT-Monitor[8]
+Other clients, whether delivered by NUT project (linkman:NUT-Monitor[1]
 GUI) or co-located (link:https://github.com/networkupstools/wmnut[WMNut])
 or third-party (see https://networkupstools.org/projects.html) would
 probably support saving their settings or "favorites".  Do not forget

docs/man/nutdrv_qx.txt

@@ -74,14 +74,14 @@ This value is truncated to units of 60 seconds.
 +
 Note that a value below 3 minutes, may cause earlier firmware versions to not switch on automatically, so it defaults to 3 minutes (i.e. 180 seconds).
 +
-This option provides a default value for *ups.delay.start* that will then be used by the driver in the automatic shutdown sequence (i.e. calling the driver with the *-k* option, calling linkman:upsdrvctl[8] with the *shutdown* option or when the +FSD+ flag is set and linkman:upsmon[8] enters its shutdown sequence): however you can change this value `on the fly' for the actual session, only for the use with instant commands, setting *ups.delay.start* with linkman:upsrw[8].
+This option provides a default value for *ups.delay.start* that will then be used by the driver in the automatic shutdown sequence (i.e. calling the driver with the *-k* option, calling linkman:upsdrvctl[8] with the *shutdown* option or when the +FSD+ flag is set and linkman:upsmon[8] enters its shutdown sequence): however you can change this value `on the fly' for the actual session, only for the use with instant commands, setting *ups.delay.start* with linkman:upsrw[1].
 
 *offdelay =* 'value'::
 Time to wait before shutting down the UPS (seconds).
 This value is truncated to units of 6 seconds (less than 60 seconds) or 60 seconds (more than 60 seconds).
 Defaults to 30 seconds.
 +
-This option provides a default value for *ups.delay.shutdown* that will then be used by the driver in the automatic shutdown sequence (i.e. calling the driver with the *-k* option, calling linkman:upsdrvctl[8] with the *shutdown* option or when the +FSD+ flag is set and linkman:upsmon[8] enters its shutdown sequence): however you can change this value "on the fly" for the actual session, only for the use with instant commands, setting *ups.delay.shutdown* with linkman:upsrw[8].
+This option provides a default value for *ups.delay.shutdown* that will then be used by the driver in the automatic shutdown sequence (i.e. calling the driver with the *-k* option, calling linkman:upsdrvctl[8] with the *shutdown* option or when the +FSD+ flag is set and linkman:upsmon[8] enters its shutdown sequence): however you can change this value "on the fly" for the actual session, only for the use with instant commands, setting *ups.delay.shutdown* with linkman:upsrw[1].
 
 *stayoff*::
 If you set stayoff in linkman:ups.conf[5] when FSD arises the UPS will call a *shutdown.stayoff* shutting down after *ups.delay.shutdown* seconds and won't return (see <<_known_problems,KNOWN PROBLEMS>>), otherwise (standard behaviour) the UPS will call *shutdown.return* shutting down after *ups.delay.shutdown* seconds and then turn on after *ups.delay.start* seconds (if mains meanwhile returned).
@@ -214,7 +214,7 @@ MASTERGUARD PROTOCOL
 *slave_addr =* 'value'::
 Make the claim function verify it's talking to the specified 'slave address' (*ups.id*).
 Safeguard against talking to the wrong one of several identical UPSes on the same USB bus.
-Note that when changing *ups.id* (through linkman:upsrw[8]) the driver will continue to talk to the UPS with the new 'slave address', but won't claim it again on restart until the *slave_addr* parameter is adjusted.
+Note that when changing *ups.id* (through linkman:upsrw[1]) the driver will continue to talk to the UPS with the new 'slave address', but won't claim it again on restart until the *slave_addr* parameter is adjusted.
 
 
 INNOVART31, INNOVART33, Q1, Q2, Q6 PROTOCOLS
@@ -463,7 +463,7 @@ This subdriver, meant to be used with the 'megatec' protocol, does *not* support
 UPS COMMANDS
 ------------
 
-This driver supports some instant commands (see linkman:upscmd[8]):
+This driver supports some instant commands (see linkman:upscmd[1]):
 
 *beeper.toggle*::
 Toggle the UPS beeper.
@@ -670,7 +670,7 @@ It no longer defaults to 0 minutes but to 3 minutes (i.e. 180 seconds) for compa
 *battnumb*::
 This option has been renamed to *battery_number*.
 
-The following options are no longer supported by this driver, you can now change them more conveniently "on the fly" calling linkman:upsrw[8] with the appropriate NUT variable -- provided that your UPS supports them.
+The following options are no longer supported by this driver, you can now change them more conveniently "on the fly" calling linkman:upsrw[1] with the appropriate NUT variable -- provided that your UPS supports them.
 
 [horizontal]
 *battpacks*:: -> *battery.packs*
@@ -883,11 +883,11 @@ linkman:blazer_ser[8],
 linkman:blazer_usb[8],
 linkman:nutupsdrv[8],
 linkman:ups.conf[5],
-linkman:upsc[8],
-linkman:upscmd[8],
+linkman:upsc[1],
+linkman:upscmd[1],
 linkman:upsdrvctl[8],
 linkman:upsmon[8],
-linkman:upsrw[8]
+linkman:upsrw[1]
 
 
 Internet Resources: