| Main Archive Page > Month Archives > spamassassin-dev archives |
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6709
--- Comment #4 from Christian Ruppert <idl0r@qasl.de> 2011-11-27 17:56:20 UTC ---
(In reply to comment #3)
> (In reply to comment #2)
> > I do set the umask in my cron job. But I think almost everybody wants the rules
> > to be world readable so making 022 as default for sa-update would make sense to
> > me, regardless of what you set as global umask.
>
> What makes sense to you or I is an installation-level decision easily handled
> with a umask setting in a wrapper script.
>
> >
> > > This might be a good thing to document but I don't see it as a bug for
> > > sa-update.
> > >
> >
> > +1
>
> Want do you think of this text added somewhere?:
>
> "The program sa-update uses the underlying operating system umask for the
> updated rule files it installs. You may wish to run sa-update from a script
> that sets the umask prior to calling sa-update. For example:
>
> #!/bin/sh
> umask 022
> sa-update"
Sounds good to me. I'd suggest to add it either to one of the README's and/or
the sa-update man page.
-- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.