trunk/README: removed an erroenous advice, refilled to 80 chars.
intrigeri
18 years ago
| 175 | 175 | a "testing state", and a "testing state into a "stable" one. |
| 176 | 176 | - First, let metche run for a while with its default TESTING_TIME and |
| 177 | 177 | STABLE_TIME configuration values (the "for a while" meaning depends on |
| 178 | how much nervous you get when you run 'df /var' every five minute; a few | |
| 179 | days is a bare minimum, a few weeks is better). | |
| 178 | how much nervous you get when you run 'df /var' every five minute; | |
| 179 | a few days is a bare minimum, a few weeks is better). | |
| 180 | 180 | - Then, have a look to the files metche has kept in $BACKUP_DIR; a simple |
| 181 | 181 | 'metche list' is enough if you're not monitoring any VServer. |
| 182 | - If there is a huge list of "unstable" but only few "testing" states, you | |
| 183 | can try lowering TESTING_TIME. If there are many more "testing" states | |
| 184 | than "stable" state, you can try lowering STABLE_TIME. It's better to | |
| 185 | only tweak one of these two parameters at a time. | |
| 182 | - If there is a huge list of "unstable" but only few "testing" states, | |
| 183 | you can try lowering TESTING_TIME. If there are many more "testing" | |
| 184 | states than "stable" state, you can try lowering STABLE_TIME. | |
| 185 | It's better to only tweak one of these two parameters at a time. | |
| 186 | 186 | - Let metche run "for a while" again... and iterate. |
| 187 | 187 | |
| 188 | 188 | c) Still despaired? |
| 189 | If this does not work for you, you can still run 'metche stabilize' from | |
| 190 | time to time, which will free some disk space. | |
| 191 | But you might also have found a weird case that metche does not handle | |
| 192 | well, call it a bug or whatever you want; you should actually e-mail us | |
| 193 | (metche AT lists DOT riseup DOT net) the output of 'metche list', your | |
| 194 | configuration file (stripped from private information), and some | |
| 195 | information about the metche version you're running. | |
| 189 | If this does not work for you, you might also have found a weird case that | |
| 190 | metche does not handle well, call it a bug or whatever you want; you | |
| 191 | should actually e-mail us (metche AT lists DOT riseup DOT net) the output | |
| 192 | of 'metche list', your configuration file (stripped from private | |
| 193 | information), and some information about the metche version you're running. |