James, I am wondering if I am using an older version of rpm here. I am using RedHat Enterprise Linux v3 and the rpm version is 4.2.1-4.4. I don't seem to have a /usr/share/doc/rpm-4.2.1/triggers file nor do I seem to have an option on the rpm command called --rollback (at least not in the man page). I do appreciate the recommendation to use triggers. I hadn't gotten to that yet in the RPM book and it seems like the way to go. I was wondering if you might have a sample spec file laying around that I might be able to extract some more info on using triggers. Thanks very much for your help. Ben Piela -----Original Message----- From: James Olin Oden [mailto:joden@xxxxxxxxxxxxx] Sent: Tuesday, April 13, 2004 11:19 AM On Tue, 13 Apr 2004, Piela, Ben wrote: > > Hello all, > > I was wondering how others manage config file changes. I would like to take > a few config files ( like syslog.conf and resolv.conf ) and, after a system > install, replace them through a "config" RPM if possible. But, the obvious > problem here is that the files are owned by other RPMs and my files will not > install via a basic rpm -ivh command. I could use --force, but that doesn't > "feel" right to me. > What we do is have the file delivered to a seperate location, and then in a trigger (or %post script) overwrite the original. Seems to work fine even with --rollback or the experimental autorollback. > The same problem arises when I receive 3rd Party vendor RPMs with basic > config files that I would like to change upon install. The vendor only > supplies binary RPMs so I cannot change the source. > > With all of this, there is also the problem of what happens when the > sysklogd RPM is upgraded. It will probably overwrite my new and improved > syslog.conf file, thus forcing me to re-install my "config" RPM. I guess > that I could live with that if I had a process that made sense. > Again, triggers are your friend, as you can have a trigger that puts your original back in place or merges its content into the new one whenever sysklogd rpm is upgraded. See: /usr/share/doc/rpm-${your_rpm_version}/triggers for more info...james Please do not transmit orders or instructions regarding a UBS account by email. The information provided in this email or any attachments is not an official transaction confirmation or account statement. For your protection, do not include account numbers, Social Security numbers, credit card numbers, passwords or other non-public information in your email. Because the information contained in this message may be privileged, confidential, proprietary or otherwise protected from disclosure, please notify us immediately by replying to this message and deleting it from your computer if you have received this communication in error. Thank you. UBS Financial Services Inc. UBS International Inc. _______________________________________________ Rpm-list mailing list Rpm-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/rpm-list
