Commit upstream/1.2 - metche

Imported Upstream version 1.2 intrigeri 12 years ago

7 changed file(s) with 194 addition(s) and 284 deletion(s). Raw diff Collapse all Expand all

+12

-0

Changelog less more

	0	1.2 (2009 12 16)
	1
	2	* stabilize: manual "metche stabilize" invocation and metche first run
	3	now send an e-mail (Closes: http://poivron.org/dev/metche/ticket/43)
	4	* documentation: tell about GnuPG's "group" option, that allows to
	5	encrypt email for multiple recipients.
	6	* EXCLUDES: added .cache, everchanging on LVM setup, and ssh private
	7	host keys.
	8	* configuration: added SEND_STABLE_REPORTS configuration setting that
	9	controls whether a report email is sent after saving a stable state;
	10	defaults to "yes" for backward compatibility.
	11
0	12	1.1 (2006 09 16)
1	13
2	14	* ververs: added Linux VServers support.

+11

-4

FAQ less more

0	0	,-------------------------------------------------------------------------------
1		\| Frequently asked0 questions about metche
	1	\| Frequently asked questions about metche
2	2	`-------------------------------------------------------------------------------
3	3
4	4	1. How are the monitored Changelog files ($CHANGELOG_FILE or

58	58	STABLE_TIME configuration values (the "for a while" meaning depends on
59	59	how much nervous you get when you run 'df /var' every five minute;
60	60	a few days is a bare minimum, a few weeks is better).
61		- Then, have a look to the files metche has kept in $BACKUP_DIR; a simple
62		'metche list' is enough if you're not monitoring any VServer.
	61	- Then, have a look to the files metche has kept in $BACKUP_DIR; a
	62	simple 'metche list' is enough if you're not monitoring any VServer.
63	63	- If there is a huge list of "unstable" but only few "testing" states,
64	64	you can try lowering TESTING_TIME. If there are many more "testing"
65	65	states than "stable" state, you can try lowering STABLE_TIME.

71	71	metche does not handle well, call it a bug or whatever you want; you
72	72	should actually e-mail us (metche AT lists DOT riseup DOT net) the output
73	73	of 'metche list', your configuration file (stripped from private
74		information), and some information about the metche version you're running.
	74	information), and some information about the metche version you're
	75	running.
75	76
76	77	7. metche does not send us any report
77	78

83	84	unstable state, such as '# metche report unstable-latest'. If the output
84	85	contains changed files you don't want to monitor, such as status files, add
85	86	them to your EXCLUDES option in metche.conf, and wait.
	87
	88	8. How do I configure e-mail encryption when sending metche reports to my
	89	sysadmin collective?
	90
	91	See the SECURITY section of metche(8).
	92

-6

README less more

0	0	metche - reducing root bus factor
1		homepage: https://poivron.org/dev/metche/
	1	homepage: https://dev.potager.org/metche/
2	2	dev team: metche AT lists DOT riseup DOT net
3	3
4	4	,-------------------------------------------------------------------------------

32	32	to $BACKUP_DIR (default: /var/lib/metche).
33	33	- send a nicely formatted email to a defined email address, listing the last
34	34	changes that have been made to the system.
35		See https://poivron.org/dev/metche/ for an example.
	35	See https://dev.potager.org/metche/ for an example.
36	36
37	37	,-------------------------------------------------------------------------------
38	38	\| BASIC USAGE

101	101	- the "system state" backups will be saved in sub-directory in BACKUP_DIR's,
102	102	called the same as the VServer;
103	103	- EMAIL_ADDRESS is not used for the VServers: the report messages will be
104		sent to the your VServer's root email address; if you're using
105		ENCRYPT_EMAIL to encrypt the report messages, make sure their public key is
106		in the host system root's keyring, trusted enough to be used blindly by
107		metche;
	104	sent to the root email address of the VServer; if you're using
	105	ENCRYPT_EMAIL to encrypt the report messages, make sure the relevant
	106	public key are in the host system root's keyring, trusted enough to be
	107	used blindly by metche;
108	108	- all other configuration variables are used as it.
109	109
110	110	Most of metche commands (namely: list, report and stabilize) support a

+14

-6

metche less more

0	0	#! /bin/bash
1	1	# -- mode: sh; sh-basic-offset: 4; indent-tabs-mode: nil; --
2	2	#
3		# SVN version: $Id: metche 176 2006-09-15 15:31:11Z intrigeri $
4		# $URL: http://poivron.org/dev/svn/metche/upstream/tags/metche-1.1/metche $
	3	# SVN version: $Id: metche 210 2009-12-01 11:21:51Z intrigeri $
	4	# $URL: https://dev.potager.org/svn/metche/upstream/trunk/metche $
5	5	#
6	6	# metche: reducing root bus factor
7	7	# Copyright (C) 2004-2006 boum.org collective - property is theft !

105	105	STABLE_TIME="3"
106	106	EMAIL_ADDRESS="root@`hostname -f`"
107	107	ENCRYPT_EMAIL="no"
	108	SEND_STABLE_REPORTS="yes"
108	109	EXCLUDES=".swp # ~ .gpg .key ifstate adjtime ld.so.cache shadow \
109		.gnupg blkid.tab* aumixrc net.enable mtab backup.d \
	110	.cache .gnupg blkid.tab* aumixrc net.enable mtab backup.d \
110	111	vdirbase run.rev vdir run.rev \
111	112	prng_exch smtp_scache.pag smtpd_scache.pag \
112		smtp_scache.dir smtpd_scache.dir local.sh"
	113	smtp_scache.dir smtpd_scache.dir local.sh \
	114	ssh_host_dsa_key* ssh_host_rsa_key*"
113	115	LOCALE="C"
114	116
115	117	VSNAMES=""

631	633	sed 's/-[0-9]*\./-latest\./'`"
632	634	fi
633	635	done
	636	if [ "${SEND_STABLE_REPORTS}" = yes ]; then
	637	echo "metche saved a new stable state: $stable." \|
	638	email "$stable"
	639	fi
634	640	}
635	641
636	642	# Print watched directory and files separated by spaces

763	769	elif no_change_since "$STABLE_TIME_MIN"; then
764	770	if changed_from "$BACKUP_DIR"/stable-latest.tar.bz2; then
765	771	save_state "stable"
766		echo "metche saved a new stable state: stable-${DATE}." \|
767		email "stable-$DATE"
	772	if [ "${SEND_STABLE_REPORTS}" = yes ]; then
	773	echo "metche saved a new stable state: stable-${DATE}." \|
	774	email "stable-$DATE"
	775	fi
768	776	debug " removing all saved testing states older" \
769	777	"than STABLE_TIME ($STABLE_TIME)."
770	778	find "$BACKUP_DIR" -name 'testing-*' \

-196

~~metche-manpage.sgml~~ less more

0		<!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook V3.1//EN"
1		"http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd">
2
3		<RefEntry id="metche">
4
5		<refmeta>
6		<refentrytitle>metche</refentrytitle>
7		<manvolnum>8</manvolnum>
8		</refmeta>
9
10		<refnamediv>
11		<refname>metche</refname>
12		<refpurpose>reducing root bus factor</refpurpose>
13		</refnamediv>
14
15		<refsynopsisdiv>
16		<cmdsynopsis>
17		<command>metche</command>
18		<arg>-h <replaceable>vserver</replaceable></arg>
19		<group choice="req">
20		<arg>report
21		<arg choice="opt">
22		<group choice="req">
23		<arg>stable</arg>
24		<arg>testing</arg>
25		<arg>unstable</arg>
26		</group>-<replaceable>YYYYMMDDHHMM</replaceable>
27		</arg>
28		</arg>
29		<arg>list</arg>
30		<arg>stabilize <arg choice="opt">testing-<replaceable>YYYYMMDDHHMM</replaceable></arg></arg>
31		</group>
32		</cmdsynopsis>
33		</refsynopsisdiv>
34
35		<refsect1 id="description">
36
37		<title>DESCRIPTION</title>
38
39		<Para>metche is a tool meant to ease collective system administration by
40		monitoring changes in the system configuration.</Para>
41
42		<Para>metche basic usage is to monitor changes in a directory, usually
43		<filename>/etc</filename> ; optionally, metche can also
44		monitor:</Para>
45		<ItemizedList>
46		<ListItem>
47		<Para>one or more user maintained changelog files,</Para>
48		</ListItem>
49		<ListItem>
50		<Para>the state of Debian packages and versions.</Para>
51		</ListItem>
52		</ItemizedList>
53
54		<Para>metche should be installed with a cronjob that regularly runs to
55		automatically save the system state as needed. These states are saved in a
56		way similar to the Debian development model:</Para>
57		<ItemizedList>
58		<ListItem>
59		<Para><emphasis>unstable</emphasis> states are saved as soon as
60		a change is detected. They are kept until a new
61		<emphasis>testing</emphasis> state appears.</Para>
62		</ListItem>
63		<ListItem>
64		<Para><emphasis>testing</emphasis> states is created from the last
65		<emphasis>unstable</emphasis> state that has not been changed
66		after a short amount of time (by default, one hour). Old
67		<emphasis>unstable</emphasis> states are deleted afterwards.</Para>
68		</ListItem>
69		<ListItem>
70		<Para><emphasis>stable</emphasis> states are created from the last
71		<emphasis>testing</emphasis> state, either manually, or after a
72		long amount of time (by default, 3 days). Old <emphasis
73		>testing</emphasis> states are deleted afterwards.</Para>
74		</ListItem>
75		</ItemizedList>
76
77		<Para>When a new <emphasis>testing</emphasis> state is saved, an email is
78		sent to a configurable address, giving an overwiew of
79		the differences with the previous <emphasis>testing</emphasis>.
80		A notification is also sent when a new <emphasis>stable</emphasis> state is
81		saved.</Para>
82
83		<Para>metche's configuration is read from
84		<filename>/etc/metche.conf</filename>. Various settings like changelog
85		monitoring or time between system state switches are described
86		there.</Para>
87
88		</refsect1>
89		<refsect1 id="options">
90
91		<title>OPTIONS</title>
92
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>
97
98		<Para>One of the following commands must be specified on the
99		command line:</Para>
100
101		<VariableList>
102
103		<VarListEntry><Term><command>report</command></Term>
104		<ListItem>
105		<Para>When run with the <command>report</command> command, metche
106		displays a report against the specified saved state, or if unspecified,
107		against the latest testing state. This is useful when you
108		have broken your system and want to know which changes have been made
109		since a given, known working, system state.</Para>
110		</ListItem>
111		</VarListEntry>
112
113		<VarListEntry><Term><command>list</command></Term>
114		<ListItem>
115		<Para>When run with the <command>list</command> command, metche
116		displays a list of all the saved states.</Para>
117		</ListItem>
118		</VarListEntry>
119
120		<VarListEntry><Term><command>stabilize</command></Term>
121		<ListItem>
122		<Para>When run with the <command>stabilize</command> command, metche
123		turns a "testing state" into a "stable state". By default, it will
124		use the last "testing state", but this can be overriden by giving
125		a specific state as argument.</Para>
126		</ListItem>
127		</VarListEntry>
128
129		<VarListEntry><Term><command>cron</command></Term>
130		<ListItem>
131		<Para>This command should not be called manually, but used from
132		a cronjob. When called, it can perform various operations like:
133		saving "unstable", "testing" or "stable" states as needed and
134		sending reports and notification if configured to do so. This command
135		does not support the <command>-h</command> option.</Para>
136		</ListItem>
137		</VarListEntry>
138
139		</VariableList>
140
141		</refsect1>
142
143		<refsect1 id="files"><title>FILES</title>
144		<Para><filename>/etc/metche.conf</filename> contains metche configuration.
145		</Para>
146
147		<Para>When configured to monitor one changelog,
148		<envar>CHANGELOG_FILE</envar> (default:
149		<filename>/root/Changelog</filename>).
150		</Para>
151
152		<Para>When configured to monitor multiple changelogs,
153		<filename>CHANGELOG_DIR/*/Changelog</filename>
154		(default: <filename>/root/changelogs</filename>).</Para>
155
156		<Para>System states are saved in
157		<envar>BACKUP_DIR</envar> (default:
158		<filename>/var/lib/metche)</filename>.</Para>
159		</refsect1>
160
161		<refsect1 id="security"><title>SECURITY</title>
162		<Para>metche is able to use GnuPG to encrypt the email it sends, but does
163		not by default; just enable the <envar>ENCRYPT_EMAIL</envar> configuration
164		option, and make sure <envar>EMAIL_ADDRESS</envar>' public key is in root's
165		keyring, trusted enough to be used blindly by metche.</Para>
166
167		<Para>When <envar>DO_DETAILS</envar> is enabled and
168		<envar>ENCRYPT_EMAIL</envar> is disabled, metche sends in <emphasis>clear
169		text email</emphasis> the changes made to the watched directory... either
170		make sure that the <envar>EXCLUDES</envar> configuration variable prevents
171		it to send sensitive information, or triple check that secure connections
172		will be used end-to-end on the email path. If unsure, set
173		<envar>EMAIL_ADDRESS</envar> configuration variable to a local mailbox.
174		Please note that <envar>EMAIL_ADDRESS</envar> is not used for VServers:
175		a VServer's report messages are sent to its root email address.</Para>
176
177		<Para>metche stores, in <envar>BACKUP_DIR</envar> (default :
178		<filename>/var/lib/metche</filename>), various backups of
179		<envar>WATCHED_DIR</envar>. Make sure that this backup place is at least as
180		secured as the source.</Para>
181		</refsect1>
182
183		<refsect1 id="bugs"><title>BUGS</title>
184		<Para>See <ulink url="https://poivron.org/dev/metche/">metche's ticket
185		system</ulink> for known bugs, missing features, and the development
186		road-map.</Para>
187		</refsect1>
188
189		<refsect1 id="author"><title>AUTHOR</title>
190		<Para>metche and this manual page were written by the boum.org collective
191		<email>metche@lists.riseup.net</email>.</Para>
192		</refsect1>
193
194		</RefEntry>
195

+140

-70

metche.8 less more

	0	'\" t
0	1	.\" Title: metche
1		.\" Author:
2		.\" Generator: DocBook XSL Stylesheets v1.70.1 <http://docbook.sf.net/>
3		.\" Date: 09/16/2006
4		.\" Manual:
5		.\" Source:
	2	.\" Author: [see the "AUTHOR" section]
	3	.\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/>
	4	.\" Date: 12/16/2009
	5	.\" Manual: [FIXME: manual]
	6	.\" Source: [FIXME: source]
	7	.\" Language: English
6	8	.\"
7		.TH "METCHE" "8" "09/16/2006" "" ""
	9	.TH "METCHE" "8" "12/16/2009" "[FIXME: source]" "[FIXME: manual]"
	10	.\" -----------------------------------------------------------------
	11	.\" * Define some portability stuff
	12	.\" -----------------------------------------------------------------
	13	.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
	14	.\" http://bugs.debian.org/507673
	15	.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
	16	.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
	17	.ie \n(.g .ds Aq \(aq
	18	.el .ds Aq '
	19	.\" -----------------------------------------------------------------
	20	.\" * set default formatting
	21	.\" -----------------------------------------------------------------
8	22	.\" disable hyphenation
9	23	.nh
10	24	.\" disable justification (adjust text to left margin only)
11	25	.ad l
	26	.\" -----------------------------------------------------------------
	27	.\" * MAIN CONTENT STARTS HERE *
	28	.\" -----------------------------------------------------------------
12	29	.SH "NAME"
13	30	metche \- reducing root bus factor
14	31	.SH "SYNOPSIS"
15		.HP 7
	32	.HP \w'\fBmetche\fR\ 'u
16	33	\fBmetche\fR [\-h\ \fIvserver\fR] {[report\ [\ {[stable]\ \|\ [testing]\ \|\ [unstable]}\-\fIYYYYMMDDHHMM\fR\ ]] \| [list] \| [stabilize\ [testing\-\fIYYYYMMDDHHMM\fR]]}
17	34	.SH "DESCRIPTION"
18	35	.PP
19		metche is a tool meant to ease collective system administration by monitoring changes in the system configuration.
	36	metche is a tool meant to ease collective system administration by monitoring changes in the system configuration\&.
20	37	.PP
21	38	metche basic usage is to monitor changes in a directory, usually
22		\fI/etc\fR
	39	/etc
23	40	; optionally, metche can also monitor:
24		.TP 3n
25		\(bu
	41	.sp
	42	.RS 4
	43	.ie n \{\
	44	\h'-04'\(bu\h'+03'\c
	45	.\}
	46	.el \{\
	47	.sp -1
	48	.IP \(bu 2.3
	49	.\}
26	50	one or more user maintained changelog files,
27		.TP 3n
28		\(bu
29		the state of Debian packages and versions.
30		.sp
31		.RE
32		.PP
33		metche should be installed with a cronjob that regularly runs to automatically save the system state as needed. These states are saved in a way similar to the Debian development model:
34		.TP 3n
35		\(bu
	51	.RE
	52	.sp
	53	.RS 4
	54	.ie n \{\
	55	\h'-04'\(bu\h'+03'\c
	56	.\}
	57	.el \{\
	58	.sp -1
	59	.IP \(bu 2.3
	60	.\}
	61	the state of Debian packages and versions\&.
	62	.RE
	63	.PP
	64	metche should be installed with a cronjob that regularly runs to automatically save the system state as needed\&. These states are saved in a way similar to the Debian development model:
	65	.sp
	66	.RS 4
	67	.ie n \{\
	68	\h'-04'\(bu\h'+03'\c
	69	.\}
	70	.el \{\
	71	.sp -1
	72	.IP \(bu 2.3
	73	.\}
36	74	\fIunstable\fR
37		states are saved as soon as a change is detected. They are kept until a new
38		\fItesting\fR
39		state appears.
40		.TP 3n
41		\(bu
	75	states are saved as soon as a change is detected\&. They are kept until a new
	76	\fItesting\fR
	77	state appears\&.
	78	.RE
	79	.sp
	80	.RS 4
	81	.ie n \{\
	82	\h'-04'\(bu\h'+03'\c
	83	.\}
	84	.el \{\
	85	.sp -1
	86	.IP \(bu 2.3
	87	.\}
42	88	\fItesting\fR
43	89	states is created from the last
44	90	\fIunstable\fR
45		state that has not been changed after a short amount of time (by default, one hour). Old
	91	state that has not been changed after a short amount of time (by default, one hour)\&. Old
46	92	\fIunstable\fR
47		states are deleted afterwards.
48		.TP 3n
49		\(bu
	93	states are deleted afterwards\&.
	94	.RE
	95	.sp
	96	.RS 4
	97	.ie n \{\
	98	\h'-04'\(bu\h'+03'\c
	99	.\}
	100	.el \{\
	101	.sp -1
	102	.IP \(bu 2.3
	103	.\}
50	104	\fIstable\fR
51	105	states are created from the last
52	106	\fItesting\fR
53		state, either manually, or after a long amount of time (by default, 3 days). Old
54		\fItesting\fR
55		states are deleted afterwards.
56		.sp
	107	state, either manually, or after a long amount of time (by default, 3 days)\&. Old
	108	\fItesting\fR
	109	states are deleted afterwards\&.
57	110	.RE
58	111	.PP
59	112	When a new
60	113	\fItesting\fR
61	114	state is saved, an email is sent to a configurable address, giving an overwiew of the differences with the previous
62		\fItesting\fR. A notification is also sent when a new
	115	\fItesting\fR\&. A notification is also sent when a new
63	116	\fIstable\fR
64		state is saved.
65		.PP
66		metche's configuration is read from
67		\fI/etc/metche.conf\fR. Various settings like changelog monitoring or time between system state switches are described there.
	117	state is saved\&.
	118	.PP
	119	metche\*(Aqs configuration is read from
	120	/etc/metche\&.conf\&. Various settings like changelog monitoring or time between system state switches are described there\&.
68	121	.SH "OPTIONS"
69	122	.PP
70	123	If

72	125	\fIVSERVER\fR
73	126	is specified, the VServer
74	127	\fIVSERVER\fR
75		is operated on instead of the host system. This, along with the
	128	is operated on instead of the host system\&. This, along with the
76	129	\fBVSNAMES\fR
77		option, allows to monitor several VServers running on the system.
	130	option, allows to monitor several VServers running on the system\&.
78	131	.PP
79	132	One of the following commands must be specified on the command line:
80		.TP 3n
	133	.PP
81	134	\fBreport\fR
	135	.RS 4
82	136	When run with the
83	137	\fBreport\fR
84		command, metche displays a report against the specified saved state, or if unspecified, against the latest testing state. This is useful when you have broken your system and want to know which changes have been made since a given, known working, system state.
85		.TP 3n
	138	command, metche displays a report against the specified saved state, or if unspecified, against the latest testing state\&. This is useful when you have broken your system and want to know which changes have been made since a given, known working, system state\&.
	139	.RE
	140	.PP
86	141	\fBlist\fR
	142	.RS 4
87	143	When run with the
88	144	\fBlist\fR
89		command, metche displays a list of all the saved states.
90		.TP 3n
	145	command, metche displays a list of all the saved states\&.
	146	.RE
	147	.PP
91	148	\fBstabilize\fR
	149	.RS 4
92	150	When run with the
93	151	\fBstabilize\fR
94		command, metche turns a "testing state" into a "stable state". By default, it will use the last "testing state", but this can be overriden by giving a specific state as argument.
95		.TP 3n
	152	command, metche turns a "testing state" into a "stable state"\&. By default, it will use the last "testing state", but this can be overriden by giving a specific state as argument\&.
	153	.RE
	154	.PP
96	155	\fBcron\fR
97		This command should not be called manually, but used from a cronjob. When called, it can perform various operations like: saving "unstable", "testing" or "stable" states as needed and sending reports and notification if configured to do so. This command does not support the
	156	.RS 4
	157	This command should not be called manually, but used from a cronjob\&. When called, it can perform various operations like: saving "unstable", "testing" or "stable" states as needed and sending reports and notification if configured to do so\&. This command does not support the
98	158	\fB\-h\fR
99		option.
	159	option\&.
	160	.RE
100	161	.SH "FILES"
101	162	.PP
102		\fI/etc/metche.conf\fR
103		contains metche configuration.
	163	/etc/metche\&.conf
	164	contains metche configuration\&.
104	165	.PP
105	166	When configured to monitor one changelog,
106	167	\fBCHANGELOG_FILE\fR
107	168	(default:
108		\fI/root/Changelog\fR).
	169	/root/Changelog)\&.
109	170	.PP
110	171	When configured to monitor multiple changelogs,
111		\fICHANGELOG_DIR/*/Changelog\fR
	172	CHANGELOG_DIR/*/Changelog
112	173	(default:
113		\fI/root/changelogs\fR).
	174	/root/changelogs)\&.
114	175	.PP
115	176	System states are saved in
116	177	\fBBACKUP_DIR\fR
117	178	(default:
118		\fI/var/lib/metche)\fR.
	179	/var/lib/metche)\&.
119	180	.SH "SECURITY"
120	181	.PP
121	182	metche is able to use GnuPG to encrypt the email it sends, but does not by default; just enable the
122	183	\fBENCRYPT_EMAIL\fR
123	184	configuration option, and make sure
124		\fBEMAIL_ADDRESS\fR' public key is in root's keyring, trusted enough to be used blindly by metche.
	185	\fBEMAIL_ADDRESS\fR\(Aq public key is in root\(Aqs keyring, trusted enough to be used blindly by metche\&. If
	186	\fBEMAIL_ADDRESS\fR
	187	is an email alias or mailing\-list\*(Aqs address, you probably want to use the
	188	\fBgroup\fR
	189	option in
	190	/root/\&.gnupg/gpg\&.conf
	191	so that metche reports are encrypted for every person subscribed to this alias or mailing\-list; for more information, see
	192	gpg(1)\&.
125	193	.PP
126	194	When
127	195	\fBDO_DETAILS\fR

129	197	\fBENCRYPT_EMAIL\fR
130	198	is disabled, metche sends in
131	199	\fIclear text email\fR
132		the changes made to the watched directory... either make sure that the
	200	the changes made to the watched directory\&.\&.\&. either make sure that the
133	201	\fBEXCLUDES\fR
134		configuration variable prevents it to send sensitive information, or triple check that secure connections will be used end\-to\-end on the email path. If unsure, set
	202	configuration variable prevents it to send sensitive information, or triple check that secure connections will be used end\-to\-end on the email path\&. If unsure, set
135	203	\fBEMAIL_ADDRESS\fR
136		configuration variable to a local mailbox. Please note that
	204	configuration variable to a local mailbox\&. Please note that
137	205	\fBEMAIL_ADDRESS\fR
138		is not used for VServers: a VServer's report messages are sent to its root email address.
	206	is not used for VServers: a VServer\*(Aqs report messages are sent to its root email address\&.
139	207	.PP
140	208	metche stores, in
141	209	\fBBACKUP_DIR\fR
142	210	(default :
143		\fI/var/lib/metche\fR), various backups of
144		\fBWATCHED_DIR\fR. Make sure that this backup place is at least as secured as the source.
	211	/var/lib/metche), various backups of
	212	\fBWATCHED_DIR\fR\&. Make sure that this backup place is at least as secured as the source\&.
145	213	.SH "BUGS"
146	214	.PP
147	215	See
148		[1]\&\fImetche's ticket system\fR
149		for known bugs, missing features, and the development road\-map.
	216	\m[blue]\fBmetche\*(Aqs ticket system\fR\m[]\&\s-2\u[1]\d\s+2
	217	for known bugs, missing features, and the development road\-map\&.
150	218	.SH "AUTHOR"
151	219	.PP
152		metche and this manual page were written by the boum.org collective
153		<metche@lists.riseup.net>.
154		.SH "REFERENCES"
155		.TP 3
156		1.\ metche's ticket system
157		\%https://poivron.org/dev/metche/
	220	metche and this manual page were written by the boum\&.org collective
	221	metche@lists\&.riseup\&.net\&.
	222	.SH "NOTES"
	223	.IP " 1." 4
	224	metche's ticket system
	225	.RS 4
	226	\%https://dev.potager.org/metche/
	227	.RE

+11

-2

metche.conf.default less more

35	35	# Encrypt emails with GnuPG ? (uncomment next line to do so)
36	36	#ENCRYPT_EMAIL="yes"
37	37
	38	# Email $EMAIL_ADDRESS after saving a stable state
	39	SEND_STABLE_REPORTS="yes"
	40
38	41	# Filename patterns to ignore (space-separated list)
39	42	# GNU tar --exclude pattern matching rules are used:
40	43	# - If a pattern matches a directory, all the files beneath it are
41	44	# recursively excluded.
42	45	# - Periods (`.') or forward slashes (`/') are not considered special for
43	46	# wildcard matches.
	47	#
	48	# Known cases where excludes are needed:
	49	# - "resolv.conf" when using resolvconf,
	50	# - "printcap" when cups browsing feature are used.
	51	#
44	52	# Example (default value):
45	53	#EXCLUDES=".swp # ~ .gpg .key ifstate adjtime ld.so.cache shadow \
46		# .gnupg blkid.tab* aumixrc net.enable mtab backup.d \
	54	# .cache .gnupg blkid.tab* aumixrc net.enable mtab backup.d \
47	55	# vdirbase run.rev vdir run.rev \
48	56	# prng_exch smtp_scache.pag smtpd_scache.pag \
49		# smtp_scache.dir smtpd_scache.dir local.sh"
	57	# smtp_scache.dir smtpd_scache.dir local.sh \
	58	# ssh_host_dsa_key* ssh_host_rsa_key*"
50	59
51	60	# Locale (will be used to feed LC_ALL)
52	61	# Warning: values different from "C" are untested.