/usr/share/doc/gnats/gnats/Management.html is in gnats 4.1.0-3.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 | <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<!-- Created by GNU Texinfo 5.2, http://www.gnu.org/software/texinfo/ -->
<head>
<title>Keeping Track: Management</title>
<meta name="description" content="Keeping Track: Management">
<meta name="keywords" content="Keeping Track: Management">
<meta name="resource-type" content="document">
<meta name="distribution" content="global">
<meta name="Generator" content="makeinfo">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<link href="index.html#Top" rel="start" title="Top">
<link href="Index.html#Index" rel="index" title="Index">
<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
<link href="index.html#Top" rel="up" title="Top">
<link href="GNATS-configuration.html#GNATS-configuration" rel="next" title="GNATS configuration">
<link href="Upgrading.html#Upgrading" rel="prev" title="Upgrading">
<style type="text/css">
<!--
a.summary-letter {text-decoration: none}
blockquote.smallquotation {font-size: smaller}
div.display {margin-left: 3.2em}
div.example {margin-left: 3.2em}
div.indentedblock {margin-left: 3.2em}
div.lisp {margin-left: 3.2em}
div.smalldisplay {margin-left: 3.2em}
div.smallexample {margin-left: 3.2em}
div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
div.smalllisp {margin-left: 3.2em}
kbd {font-style:oblique}
pre.display {font-family: inherit}
pre.format {font-family: inherit}
pre.menu-comment {font-family: serif}
pre.menu-preformatted {font-family: serif}
pre.smalldisplay {font-family: inherit; font-size: smaller}
pre.smallexample {font-size: smaller}
pre.smallformat {font-family: inherit; font-size: smaller}
pre.smalllisp {font-size: smaller}
span.nocodebreak {white-space:nowrap}
span.nolinebreak {white-space:nowrap}
span.roman {font-family:serif; font-weight:normal}
span.sansserif {font-family:sans-serif; font-weight:normal}
ul.no-bullet {list-style: none}
-->
</style>
</head>
<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF" vlink="#800080" alink="#FF0000">
<a name="Management"></a>
<div class="header">
<p>
Next: <a href="Locations.html#Locations" accesskey="n" rel="next">Locations</a>, Previous: <a href="Installation.html#Installation" accesskey="p" rel="prev">Installation</a>, Up: <a href="index.html#Top" accesskey="u" rel="up">Top</a> [<a href="index.html#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="Index.html#Index" title="Index" rel="index">Index</a>]</p>
</div>
<hr>
<a name="GNATS-Administration"></a>
<h2 class="chapter">4 <small>GNATS</small> Administration</h2>
<a name="index-administering-GNATS"></a>
<a name="index-managing-GNATS"></a>
<a name="index-GNATS-management"></a>
<a name="index-duties-for-gnats_002dadmin"></a>
<p>In daily usage, <small>GNATS</small> 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 <small>GNATS</small> configuration at some point:
</p>
<dl compact="compact">
<dt><em>emptying the <code>pending</code> directory</em></dt>
<dd><a name="index-emptying-the-pending-directory"></a>
<p>If a Problem Report arrives with a <code>Category</code> value that is
unrecognized by the <samp>categories</samp> file, or if that field is missing,
<small>GNATS</small> places the PR in the <samp>pending</samp><!-- /@w --> directory
(see <a href="Locations.html#Locations">Where <small>GNATS</small> lives</a>). PRs
submitted in free-form by email will always be filed in the
<samp>pending</samp><!-- /@w --> directory. If so configured, <small>GNATS</small> sends a
notice to the <code>gnats-admin</code> and to the party responsible for that
submitter (as listed in the <samp>submitters</samp> file) when this occurs.
</p>
<p>To have these "categoryless" PRs filed correctly, you can then use a
<small>GNATS</small> tool such as <code>edit-pr</code> to set the correct category of
each PR in the <samp>pending</samp> directory.
</p>
<p>In order to protect yourself from problems caused by full disks, you
should arrange to have all mail that is sent to the <small>GNATS</small> database
copied to a log file (<a href="Aliases.html#Aliases">Setting up mail aliases</a>). Then,
should you run out of disk space, and an empty file ends up in the
database’s <samp>pending</samp> directory, you need only look in the log file,
which should still contain the full message that was submitted.
</p>
</dd>
<dt><em>adding another database</em></dt>
<dd><a name="index-adding-another-database"></a>
<a name="index-mkdb"></a>
<p><small>GNATS</small> supports multiple databases. If you find at some point that
you need to add another database to your server, the <code>mkdb</code> tool
does most of the work for you. See <a href="mkdb.html#mkdb">Adding
another database</a>.
</p>
</dd>
<dt><em>adding new categories</em></dt>
<dd><a name="index-adding-a-problem-category"></a>
<a name="index-mkcat"></a>
<p>Most installations of <small>GNATS</small> will only require you to add a new line
to the <samp>categories</samp><!-- /@w --> file. The category directory will then be
created automatically as needed. However, if automatic directory
creation has been switched off in the <samp>dbconfig</samp> file
(see <a href="dbconfig-file.html#dbconfig-file">The <code>dbconfig</code> file</a>), you need to use the
<samp>mkcat</samp> program.
</p>
</dd>
<dt><em>removing categories</em></dt>
<dd><a name="index-removing-a-problem-category"></a>
<a name="index-rmcat"></a>
<p>To remove a category, you need to make sure the relevant subdirectory is
empty (in other words, make sure no PRs exist for the category you wish
to remove). You can then remove the category listing from the
<samp>categories</samp> file, and invoke
</p>
<div class="smallexample">
<pre class="smallexample">rmcat <var>category…</var>
</pre></div>
<p>to remove <var>category</var> (any number of categories may be specified on
the command line to <code>rmcat</code>, so long as they abide by the above
constraints).
</p>
</dd>
<dt><em>adding and removing maintainers</em></dt>
<dd><a name="index-adding-and-removing-maintainers"></a>
<p>Edit the <samp>responsible</samp> file to add a new maintainer or to remove an
existing maintainer. See <a href="responsible-file.html#responsible-file">The <code>responsible</code> file</a>.
</p>
</dd>
<dt><em>building a new index</em></dt>
<dd><a name="index-building-a-new-index"></a>
<a name="index-gen_002dindex"></a>
<p>If your index becomes corrupted, or if you wish to generate a new one
for some reason, use the program <code>gen-index</code>
(see <a href="gen_002dindex.html#gen_002dindex">Regenerating the index</a>).
</p>
</dd>
<dt><em>pruning log files</em></dt>
<dd><a name="index-pruning-log-files"></a>
<p>Log files often grow to unfathomable proportions. As with gardening, it
is best to prune these as they grow, lest they take over your disk and
leave you with no room to gather more Problem Reports. If you keep log
files, be sure to keep an eye on them. (See <a href="Aliases.html#Aliases">Setting up mail
aliases</a>.)
</p>
</dd>
<dt><em>BACKING UP YOUR DATA</em></dt>
<dd><a name="index-BACK-UP-YOUR-DATA"></a>
<p>Any database is only useful if its data remains uncorrupted and safe.
Performing periodic backups ensures that problems like disk crashes and
data corruption are reversible.
</p>
</dd>
</dl>
<p>See <a href="Locations.html#Locations">Where <small>GNATS</small> lives</a>.
</p>
<table class="menu" border="0" cellspacing="0">
<tr><td align="left" valign="top">• <a href="GNATS-configuration.html#GNATS-configuration" accesskey="1">GNATS configuration</a>:</td><td> </td><td align="left" valign="top">Overview of GNATS configuration
</td></tr>
<tr><td align="left" valign="top">• <a href="databases-file.html#databases-file" accesskey="2">databases file</a>:</td><td> </td><td align="left" valign="top">The databases file
</td></tr>
<tr><td align="left" valign="top">• <a href="dbconfig-file.html#dbconfig-file" accesskey="3">dbconfig file</a>:</td><td> </td><td align="left" valign="top">The dbconfig file
</td></tr>
<tr><td align="left" valign="top">• <a href="Other-config-files.html#Other-config-files" accesskey="4">Other config files</a>:</td><td> </td><td align="left" valign="top">Configuration files
</td></tr>
<tr><td align="left" valign="top">• <a href="send_002dpr_002econf-file.html#send_002dpr_002econf-file" accesskey="5">send-pr.conf file</a>:</td><td> </td><td align="left" valign="top">The send-pr.conf file
</td></tr>
<tr><td align="left" valign="top">• <a href="Admin-files.html#Admin-files" accesskey="6">Admin files</a>:</td><td> </td><td align="left" valign="top">Administrative data files
</td></tr>
<tr><td align="left" valign="top">• <a href="Admin-utils.html#Admin-utils" accesskey="7">Admin utils</a>:</td><td> </td><td align="left" valign="top">Administrative utilities
</td></tr>
<tr><td align="left" valign="top">• <a href="Internal-utils.html#Internal-utils" accesskey="8">Internal utils</a>:</td><td> </td><td align="left" valign="top">Internal utilities
</td></tr>
</table>
<hr>
<div class="header">
<p>
Next: <a href="Locations.html#Locations" accesskey="n" rel="next">Locations</a>, Previous: <a href="Installation.html#Installation" accesskey="p" rel="prev">Installation</a>, Up: <a href="index.html#Top" accesskey="u" rel="up">Top</a> [<a href="index.html#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="Index.html#Index" title="Index" rel="index">Index</a>]</p>
</div>
</body>
</html>
|