You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@spamassassin.apache.org by bu...@bugzilla.spamassassin.org on 2014/04/01 15:49:07 UTC
[Bug 6994] SpamAssassin's perm test is invalid; disable & let user
manage security?
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6994
Kevin A. McGrail <km...@pccc.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |RESOLVED
Resolution|--- |FIXED
--- Comment #12 from Kevin A. McGrail <km...@pccc.com> ---
(In reply to linda w from comment #11)
> Simpler would be to change the system line:
> system("chacl -B log 2>/dev/null || setfacl -b log 2>/dev/null")
>
> Then you have your test for existence and execution in 1 line.
>
> That assumes the error message was on stderr, else redirect stdout
> as well.
> The point of using chacl || setfacl, was to pick up which ever
> (if any) was on the system. If none are on the system, unlikely
> ACLs are in use, so partial or complete failure is ok...
>
> Good until someone comes up with other commonly used routines
> to manage / change acls.
Thanks Linda. Elegantly simple.
svn commit -m 'Small change for systems with ACLs in testing - bug 6994'
Sending t/SATest.pm
Transmitting file data .
Committed revision 1583670.
--
You are receiving this mail because:
You are the assignee for the bug.