Node:Management, Next:Locations, Previous:Installation, Up:Top
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:
Categoryvalue that is unrecognized by the
categoriesfile, or if that field is missing, GNATS places the PR in the
pendingdirectory (see Where GNATS lives). PRs submitted in free-form by email will always be filed in the
pendingdirectory. If so configured, GNATS sends a notice to the
gnats-adminand to the party responsible for that submitter (as listed in the
submittersfile) 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
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
pending directory, you need only look in the log file,
which should still contain the full message that was submitted.
mkdbtool does most of the work for you. See Adding another database.
categoriesfile. The category directory will then be created automatically as needed. However, if automatic directory creation has been switched off in the
dbconfigfile (see The
dbconfigfile), you need to use the
categoriesfile, and invoke
to remove category (any number of categories may be specified on
the command line to
rmcat, so long as they abide by the above
responsiblefile to add a new maintainer or to remove an existing maintainer. See The
gen-index(see Regenerating the index).
See Where GNATS lives.