On Thu, 16 Apr 1998, Rick L. Mantooth wrote:
> Doug,
> Not really answering your question, but I've picked up the habit
> of "rpm -qlp newpackage.rpm" and looking for any files that are gonna
> get clobbered.
> > I want to upgrade to the new rpm. I am upgrading the bind on an ISp's
> > name server. At home when i upgrade bind and sendmail it is no problem if
> > config files and wha not get clobbered. But here at work I can't kill our
> > files like that. Is thier an easy way to make the upgrade invisible so
> > that nothing needs to be fixed or updated after the rpm'ing?
Well first off, you have more than one nameserver, so you only have to
upgrade one at a time and let the backup server do what it's suppossed to
do.
The zone files for forward and reverse lookups shouldn't change a whit.
That leaves the config file in /etc.
If I wanted to be paranoid, I'd set up a test box just like my current
name server, run the upgrade, see what I need to fix, then have the
neessary files ready to go.
After that preparation, shutting down named, rpm -U <package>, moving in
the necessary files, and starting the new named shouldn't take long.
Steve
--
PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES!
http://www.redhat.com/RedHat-FAQ /RedHat-Errata /RedHat-Tips /mailing-lists
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject.
