In daily usage, gnats is self-maintaining. However, there are various administrative duties which need to be performed periodically. Also, requirements may change with time, so it may be necessary to make changes to the gnats configuration at some point:
pending
directoryCategory
value that is
unrecognized by the categories file, or if that field is missing,
gnats places the PR in the pending directory
(see Where gnats lives). PRs
submitted in free-form by email will always be filed in the
pending directory. If so configured, gnats sends a
notice to the gnats-admin
and to the party responsible for that
submitter (as listed in the submitters file) when this occurs.
To have these "categoryless" PRs filed correctly, you can then use a
gnats tool such as edit-pr
to set the correct category of
each PR in the pending directory.
In order to protect yourself from problems caused by full disks, you
should arrange to have all mail that is sent to the gnats database
copied to a log file (Setting up mail aliases). Then,
should you run out of disk space, and an empty file ends up in the
database's pending directory, you need only look in the log file,
which should still contain the full message that was submitted.
mkdb
tool
does most of the work for you. See Adding another database.
dbconfig
file), you need to use the
mkcat program.
rmcat category...
to remove category (any number of categories may be specified on
the command line to rmcat
, so long as they abide by the above
constraints).
responsible
file.
gen-index
(see Regenerating the index).
See Where gnats lives.