Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 227622 - Unable to pass argument to sa-update
Summary: Unable to pass argument to sa-update
Alias: None
Product: Fedora
Classification: Fedora
Component: spamassassin
Version: 6
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Warren Togami
QA Contact:
Whiteboard: bzcl34nup
Depends On:
TreeView+ depends on / blocked
Reported: 2007-02-07 04:38 UTC by Milan Kerslager
Modified: 2008-05-06 19:10 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2008-05-06 19:10:42 UTC

Attachments (Terms of Use)

Description Milan Kerslager 2007-02-07 04:38:13 UTC
As there is a standartized cron script now to utilize sa-update, please allow
pass arguments to this command. Use /etc/sysconfig/spamassassin to set
$SAUPDATEOPT, and use this in /usr/share/spamassassin/sa-update.cron:

if [ -f /etc/sysconfig/spamassassin ]; then
        . /etc/sysconfig/spamassassin
/usr/bin/sa-update $SAUPDATEOPT

These argument are necessary to be able to alter sa-update default behaviour.

Also I dislike output (echo commands with mailing to root by cron daemon) in
this file even there is no (error) output. Please remove it along with tee
commad and redirection of output in the file /etc/cron.d/sa-update. Unix-like
style is to report nothing when there is no error.

There is also a possibility to add -D (--debug [area=n,...]) argument to the
sa-update to get output mailed if one need it.

Thank you.

Comment 1 Warren Togami 2007-02-19 18:47:02 UTC
I have since silenced it so it no longer generates mail.

What regular use case is there to have options to sa-update? 

Debug is not a good case, because you can just add it manually to the script and
watch it temporarily during your debugging.

Comment 2 Jason Tibbitts 2007-02-19 18:51:26 UTC
I'd say the configuration of alternate or additional channels is a reasonable
use case.

Comment 3 Milan Kerslager 2007-02-19 20:18:30 UTC
Yes. That's it. Thank you a lot.

Comment 4 Bug Zapper 2008-04-04 06:07:26 UTC
Fedora apologizes that these issues have not been resolved yet. We're
sorry it's taken so long for your bug to be properly triaged and acted
on. We appreciate the time you took to report this issue and want to
make sure no important bugs slip through the cracks.

If you're currently running a version of Fedora Core between 1 and 6,
please note that Fedora no longer maintains these releases. We strongly
encourage you to upgrade to a current Fedora release. In order to
refocus our efforts as a project we are flagging all of the open bugs
for releases which are no longer maintained and closing them.

If this bug is still open against Fedora Core 1 through 6, thirty days
from now, it will be closed 'WONTFIX'. If you can reporduce this bug in
the latest Fedora version, please change to the respective version. If
you are unable to do this, please add a comment to this bug requesting
the change.

Thanks for your help, and we apologize again that we haven't handled
these issues to this point.

The process we are following is outlined here:

We will be following the process here: to ensure this
doesn't happen again.

And if you'd like to join the bug triage team to help make things
better, check out

Comment 5 Bug Zapper 2008-05-06 19:10:41 UTC
This bug is open for a Fedora version that is no longer maintained and
will not be fixed by Fedora. Therefore we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen thus bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.