Commit a3a1160c18e2574e6c13aae5d883c46bb24629ab - metche

Fix a typo and some wrapping in FAQ. Lunar 17 years ago

1 changed file(s) with 5 addition(s) and 4 deletion(s). Raw diff Collapse all Expand all

-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