upstream/trunk/FAQ: added a question/answer about everchanging files and how to
diagnose them.
intrigeri
17 years ago
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 | 74 | information), and some information about the metche version you're running. |
75 | ||
76 | 7. metche does not send us any report | |
77 | ||
78 | It could be an e-mail problem, but, more probably, one of your installed | |
79 | programs violates the FHS and writes one or more ever-changing files in /etc | |
80 | instead of /var. This prevents metche of turning any "unstable" state into | |
81 | a "testing" state, and therefore to send you any report. | |
82 | You can diagnose this by asking metche to generate a report against a recent | |
83 | unstable state, such as '# metche report unstable-latest'. If the output | |
84 | contains changed files you don't want to monitor, such as status files, add | |
85 | them to your EXCLUDES option in metche.conf, and wait. |