Description:
This is obsolete. You should be running L<run-remstats2 instead.
run-remstats
is the main script for a remstats collection machine.
As a simplified overview:
For each of these programs, run-remstats
will set a timer (see watchdogtimer
in the general config-file). If the timer expires and the
program is still running, run-remstats
will kill that process. This avoids the
problem of a hanging collector hanging the whole remstats cycle.
It also manages a lock-file to make sure that two instances don't run
concurrently. The lock-file's name is based on the name of the run-remstats
script. (See Running multiple copies of run-remstats below.)
It keeps a status file in the configured temp directory (/var/lib/remstats/tmp
by default) which is used by monitor to show where the run-remstats
process has gotten to.
When starting, it will also look for a file in the tmp directory called
STOP-run-remstats
(default), and if it exists, will refuse to run at all.
Running multiple copies of run-remstats
If you symlink run-remstats
to run-remstats-XXX
, then the
default configuration directory for run-remstats-XXX
will be
/etc/remstats/config-XXX
. Since the lock-file is named for the script
which invokes it, you won't have collisions between
the two instances, as long as your configuration files don't
conflict. You can have multiple collector-only instances collecting
data which is formatted by a single pagemaker instance, (in theory)
but this will require at least three config-dirs which must be
closely co-ordinated. If you want to do this for performance
reasons, I do plan to address this in future.