Author: Description: Adapt user guide to Debian packaging --- a/doc/userguide.pod.in +++ b/doc/userguide.pod.in @@ -26,13 +26,14 @@ The steps below will explain you how to make the thing running. -B. Follow the I document, -all prerequisits and necessary steps are described there. +B please read the README.Debian file in +/usr/share/doc/torrus-common directory for some Debian-specific +information. B. The executables reside in F<@pkgbindir@/>. You normally don't need to access this directory, because the commandline wrapper, C, is installed -in a usual execution path (F<@bindir@>). +in a usual execution path (F). All site-specific behaviour is controlled by configuration files in F<@siteconfdir@/>. Usually you need to change F only. In this file, you @@ -192,12 +193,6 @@ process, and write only error messages in its log file, F<@logdir@/collector.treename.log>. -There is a file that is created by C<./configure>, called F. -You may place it into a directory where your system looks for startup scripts -(F on Solaris and some Linuxes, F -on FreeBSD). Probably you need to rename and edit the script before using. -Note that it also executes another daemon, C. - The C daemon is used for monitoring the thresholds in the data files. For more details, see the I, in the section about monitor definitions. @@ -393,6 +388,9 @@ =head3 Amending autogenerated XML files with XUpdate +B not all the utilities mentioned in this section +are packaged for Debian at this time. + Sometimes there is a need to modify the configuration generated by C. Modifying the generated XML files by hand would not be a good option: it would need some manual work every time you update @@ -567,6 +565,9 @@ =head3 Several Torrus instances on one server +B in the current packaging scheme only one Torrus +instance per server is supported. + Sometimes it is necessary to have a separate instance of Torrus for testing purposes on the same server as the production installation. In the example below, a completely autonomous installation of Torrus is