From: "Justin Patrin" <papercrane@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] dispatch-conf spells disaster
Date: Wed, 18 Oct 2006 08:14:59 -0700 [thread overview]
Message-ID: <432beae0610180814p22fb16d9s935b4601fb415555@mail.gmail.com> (raw)
In-Reply-To: <20061015020925.23363.qmail@web31713.mail.mud.yahoo.com>
On 10/14/06, maxim wexler <blissfix@yahoo.com> wrote:
> Hello group,
>
> As I expected it would, dispatch-conf
> over-wrote/corrupted a lot of files without giving me
> a chance to stop it. It left no log(file was empty)in
> /var/log/dispatch-conf.log. or any record of its
> passing that I can find.
>
Why did you expect this and, if you expected it, why didn't you take
steps to back things up.
dispatch-conf normally works just fine. Perhaps you set some incorrect
options in your dispatch-conf conf file, such as auto-updating of all
files. You also should have set up RCS backups of your conf files so
that you can move back.
--
Justin Patrin
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2006-10-18 15:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-15 2:09 [gentoo-user] dispatch-conf spells disaster maxim wexler
2006-10-15 2:24 ` Bo Ørsted Andresen
2006-10-15 15:34 ` [gentoo-user] dispatch-conf spells disaster-RESOLVED maxim wexler
2006-10-15 17:05 ` Neil Bothwick
2006-10-16 20:26 ` [gentoo-user] dispatch-conf spells disaster-RESOLVED? maxim wexler
2006-10-16 20:30 ` Bo Ørsted Andresen
2006-10-18 5:26 ` [gentoo-user] " Alexander Skwar
2006-10-16 21:04 ` [gentoo-user] " Neil Bothwick
2006-10-15 17:10 ` [gentoo-user] dispatch-conf spells disaster-RESOLVED Boyd Stephen Smith Jr.
2006-10-16 20:53 ` maxim wexler
2006-10-17 12:45 ` Boyd Stephen Smith Jr.
2006-10-17 13:00 ` Bo Ørsted Andresen
2006-10-18 15:14 ` Justin Patrin [this message]
2006-10-18 15:19 ` [gentoo-user] dispatch-conf spells disaster Justin Patrin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=432beae0610180814p22fb16d9s935b4601fb415555@mail.gmail.com \
--to=papercrane@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox