On 06-03-12 23:03, Jason Parker wrote: [snip]
It should only set them if the directory does not exist. If it's changing them, something is very seriously broken.
An RPM which updates a previous version will change the user/group & permissions of any existing directory or file as it is instructed to.
I just tested it on CentOS 6 to verify: 1) RPM #1 installs /etc/test and file /etc/test/mytest.txt user/group = asterisk/asterisk, dir/file perms are 0750/0640 2) manually change user/group/perms of directory/file to something else 3) RPM #2 updates RPM #1. RPM #2 sets user/group to asterisk/asterisk and dir/file perms to 0750/0640. So it's back to the original settings from the spec file.Not setting user/group ownership and permissions will make rpmbuild use defaults (iirc root:root for ownership, 755 perms for directories and 644 perms for files).
Regards, Patrick -- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
[Gnu Gatekeeper] [IETF Sipping] [Info Cyrus] [ALSA User] [Fedora Linux Users] [DCCP] [Gimp] [100% Free Online Dating] [Yosemite News] [Arts & Crafts] [Yosemite Photos] [Deep Creek Hot Springs] [Yosemite Campsites] [ISDN Cause Codes]