[Bug 462163] Review Request: checkdns - A Domain Name Server analysis and reporting tool

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.


https://bugzilla.redhat.com/show_bug.cgi?id=462163





--- Comment #10 from John Guthrie <guthrie at counterexample.org>  2008-11-26 00:06:26 EDT ---
(In reply to comment #7)
> - I did not examine carefully the program, but I think that you can eliminate
> the need of suid group for the checkdns folder if - in %post - you create a
> checkdns user and use
>      chown checkdns.apache  /var/www/html/checkdns
>      chmod 755 /var/www/html/checkdns
>      make sure that the checkdns program is run as the checkdns user (which is
>              extremely easy to do in cron)
> The only drawback is that if the program is run by another user (in a console),
> the HTML files will not be created with the correct ownership. But as the
> output is sent to the console, it can be redirected anywhere.

I'm a little confused.  Why would I want to do all of that in %post?  Why not
in %pre, and just set the ownership and permissions in the %files section? 
Unless I'm mistaken, what you are proposing would require changing
perms/ownership after they have been placed into the RPM database, with the
result that rpm -V will always flag them as having been changed.  Am I missing
something?

(In addition, every other package that I have seen add users or groups has done
so in %pre.)

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.