I've rewritten fix-permissions.sh to use absolute paths for find and
chmod, and removed the "-user ${USER}" check. I believe this modified
script should be safe to be configured setuid root. That way, anybody
could run it and clean up anyone's fix-permissions errors, even if someone
else forgot.
I know we've been talking about setting it up as a cron job for months,
but apparently that's politically difficult (I suppose that it could be
more maintenance work). In this proposal, all I want is for somebody to
mark this version of the script setuid root; it's a one-time-only chmod
command.
Unlike the cron proposal, I believe this could actually happen this week
if we decided it should happen.
Agreed?
-------------
echo Checking /www/people.apache.org/repo/m2-snapshot-repository
/usr/bin/find /www/people.apache.org/repo/m2-snapshot-repository ! -perm 775
-type d -exec /bin/chmod 775 {} \; -print
/usr/bin/find /www/people.apache.org/repo/m2-snapshot-repository ! -perm 664
-iname maven-metadata.xml* -exec /bin/chmod 664 {} \; -print
echo Checking /www/people.apache.org/repo/m2-ibiblio-rsync-repository
/usr/bin/find /www/people.apache.org/repo/m2-ibiblio-rsync-repository ! -perm
775 -type d -exec /bin/chmod 775 {} \; -print
/usr/bin/find /www/people.apache.org/repo/m2-ibiblio-rsync-repository ! -perm
664 -iname maven-metadata.xml* -exec /bin/chmod 664 {} \; -print
echo Checking /www/people.apache.org/repo/m2-incubating-repository
/usr/bin/find /www/people.apache.org/repo/m2-incubating-repository ! -perm 775
-type d -exec /bin/chmod 775 {} \; -print
/usr/bin/find /www/people.apache.org/repo/m2-incubating-repository ! -perm 664
-iname maven-metadata.xml* -exec /bin/chmod 664 {} \; -print
-------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
