| 1 |
On 10/18/06, Justin Patrin <papercrane@×××××.com> wrote: |
| 2 |
> On 10/14/06, maxim wexler <blissfix@×××××.com> wrote: |
| 3 |
> > Hello group, |
| 4 |
> > |
| 5 |
> > As I expected it would, dispatch-conf |
| 6 |
> > over-wrote/corrupted a lot of files without giving me |
| 7 |
> > a chance to stop it. It left no log(file was empty)in |
| 8 |
> > /var/log/dispatch-conf.log. or any record of its |
| 9 |
> > passing that I can find. |
| 10 |
> > |
| 11 |
> |
| 12 |
> Why did you expect this and, if you expected it, why didn't you take |
| 13 |
> steps to back things up. |
| 14 |
> |
| 15 |
> dispatch-conf normally works just fine. Perhaps you set some incorrect |
| 16 |
> options in your dispatch-conf conf file, such as auto-updating of all |
| 17 |
> files. You also should have set up RCS backups of your conf files so |
| 18 |
> that you can move back. |
| 19 |
> |
| 20 |
|
| 21 |
nm, looks like the FUD has been dealt with in further replies. |
| 22 |
|
| 23 |
-- |
| 24 |
Justin Patrin |
| 25 |
-- |
| 26 |
gentoo-user@g.o mailing list |
Archives