15 | 15 |
<refsynopsisdiv>
|
16 | 16 |
<cmdsynopsis>
|
17 | 17 |
<command>metche</command>
|
18 | |
<arg>-h <replaceable>host</replaceable></arg>
|
|
18 |
<arg>-h <replaceable>vserver</replaceable></arg>
|
19 | 19 |
<group choice="req">
|
20 | |
<arg>cron</arg>
|
21 | |
<arg>report
|
|
20 |
<arg>report
|
22 | 21 |
<arg choice="opt">
|
23 | 22 |
<group choice="req">
|
24 | |
<arg>stable</arg>
|
25 | |
<arg>testing</arg>
|
26 | |
<arg>unstable</arg>
|
27 | |
</group>-<replaceable>YYYYMMDDHHMM</replaceable>
|
|
23 |
<arg>stable</arg>
|
|
24 |
<arg>testing</arg>
|
|
25 |
<arg>unstable</arg>
|
|
26 |
</group>-<replaceable>YYYYMMDDHHMM</replaceable>
|
28 | 27 |
</arg>
|
29 | 28 |
</arg>
|
30 | |
<arg>list</arg>
|
31 | |
<arg>stabilize <arg choice="opt">testing-<replaceable>YYYYMMDDHHMM</replaceable></arg></arg>
|
|
29 |
<arg>list</arg>
|
|
30 |
<arg>stabilize <arg choice="opt">testing-<replaceable>YYYYMMDDHHMM</replaceable></arg></arg>
|
32 | 31 |
</group>
|
33 | 32 |
</cmdsynopsis>
|
34 | 33 |
</refsynopsisdiv>
|
|
37 | 36 |
|
38 | 37 |
<title>DESCRIPTION</title>
|
39 | 38 |
|
40 | |
<Para>metche is a tool meant to facilitate collective sysadmin by
|
|
39 |
<Para>metche is a tool meant to ease collective system administration by
|
41 | 40 |
monitoring changes in the system configuration.</Para>
|
42 | 41 |
|
43 | 42 |
<Para>metche basic usage is to monitor changes in a directory, usually
|
|
91 | 90 |
|
92 | 91 |
<title>OPTIONS</title>
|
93 | 92 |
|
94 | |
<Para>If <command>-h</command> <emphasis>HOST</emphasis> is specified,
|
95 | |
<filename>/etc/metche/HOST.conf</filename> is used instead of
|
96 | |
<filename>/etc/metche.conf</filename>. This, along with the
|
97 | |
<envar>VSERVER_EXEC_PREFIX</envar> option, allows to monitor several
|
98 | |
vservers running on a system.</Para>
|
|
93 |
<Para>If <command>-h</command> <emphasis>VSERVER</emphasis> is specified,
|
|
94 |
the VServer <emphasis>VSERVER</emphasis> is operated on instead of
|
|
95 |
the host system. This, along with the <envar>VSNAMES</envar> option,
|
|
96 |
allows to monitor several VServers running on the system.</Para>
|
99 | 97 |
|
100 | 98 |
<Para>One of the following commands must be specified on the
|
101 | 99 |
command line:</Para>
|
|
130 | 128 |
<Para>This command should not be called manually, but used from
|
131 | 129 |
a cronjob. When called, it can perform various operations like:
|
132 | 130 |
saving "unstable", "testing" or "stable" states as needed and
|
133 | |
sending reports and notification if configured to do so.</Para>
|
|
131 |
sending reports and notification if configured to do so. This command
|
|
132 |
does not support the <command>-h</command> option.</Para>
|
134 | 133 |
</ListItem>
|
135 | 134 |
|
136 | 135 |
</VariableList>
|
|
138 | 137 |
</refsect1>
|
139 | 138 |
|
140 | 139 |
<refsect1 id="files"><title>FILES</title>
|
141 | |
<Para><filename>/etc/metche.conf</filename> or
|
142 | |
<filename>/etc/metche/*.conf</filename> contain metche configuration.
|
|
140 |
<Para><filename>/etc/metche.conf</filename> contains metche configuration.
|
143 | 141 |
</Para>
|
144 | 142 |
|
145 | 143 |
<Para>When configured to monitor one changelog,
|
146 | |
<filename><envar>CHANGELOG_FILE</envar></filename> (default
|
|
144 |
<filename><envar>CHANGELOG_FILE</envar></filename> (default:
|
147 | 145 |
<filename>/root/Changelog</filename>).
|
148 | 146 |
</Para>
|
149 | 147 |
|
150 | 148 |
<Para>When configured to monitor multiple changelogs,
|
151 | 149 |
<filename><envar>CHANGELOG_DIR</envar>/*/Changelog</filename>
|
152 | |
(default : <filename>/root/changelogs</filename>).</Para>
|
|
150 |
(default: <filename>/root/changelogs</filename>).</Para>
|
153 | 151 |
|
154 | 152 |
<Para>System states are saved in
|
155 | |
<filename><envar>BACKUP_DIR</envar></filename> (default
|
|
153 |
<filename><envar>BACKUP_DIR</envar></filename> (default:
|
156 | 154 |
<filename>/var/lib/metche)</filename>.</Para>
|
157 | 155 |
</refsect1>
|
158 | 156 |
|
|
165 | 163 |
<Para>In its default setup (<envar>ENCRYPT_EMAIL</envar> configuration
|
166 | 164 |
option disabled) metche sends in <emphasis>clear text email</emphasis> the
|
167 | 165 |
changes made to the watched directory... either make sure that the
|
168 | |
<envar>TAR_OPTS</envar> configuration variable prevents it to send sensitive
|
|
166 |
<envar>EXCLUDES</envar> configuration variable prevents it to send sensitive
|
169 | 167 |
information, or triple check that secure connections will be used end-to-end
|
170 | 168 |
on the email path. If unsure, set <envar>EMAIL_ADDRESS</envar> configuration
|
171 | 169 |
variable to a local mailbox.</Para>
|
|
183 | 181 |
</refsect1>
|
184 | 182 |
|
185 | 183 |
<refsect1 id="author"><title>AUTHOR</title>
|
186 | |
<Para>This manual page was written by the boum collective
|
187 | |
<email>boum@anargeek.net</email>.</Para>
|
|
184 |
<Para>metche and this manual page were written by the boum collective
|
|
185 |
<email>metche@lists.riseup.net</email>.</Para>
|
188 | 186 |
</refsect1>
|
189 | 187 |
|
190 | 188 |
</RefEntry>
|