On Friday 04 August 2006 9:33 am, Theo Van Dinter wrote:

> The problem is, yet again, of assumption.  The code assumes that if the
> update directory exists, that certain channel files will be in there
> because it creates them (aka: channel.cf and channel.pre).  So when an
> update occurs, the code dutifully removes those files before installing
> the update where it'll recreate them for the new files.  Unfortunately,
> there's a flaw in the assumption wherein the channel files only _may_
> exist -- if sa-update doesn't have anything to put into the file,
> it doesn't bother writing it out.  So in the end we get this warning
> because the attempt to remove the non-existant file failed.
>
> I had also forgotten that the "don't create if empty" bit was in the
> code, hence my "Crap!" when I was reading through and found it. :|
>
> > channel: attempt to rm channel pre file failed, attempting to continue
> > anyway at /usr/bin/sa-update line 691.
> > /bin/sh: line 1: service: command not found
> >
> > Or is that also part of the bug?
>
> The "service: command not found" line?  No, that's something you're
> calling outside of sa-update.  My guess is you're trying something like:
>
> sa-update && service spamassassin restart
>
> which assumes you're on an OS with the "service" command and that it's
> in your path (amongst other things).

Yes, I'm running it as a cronjob with sa-update && service spamassassin 
restart. It worked the first time it ran and it must have worked today as 
the "updates.spamassassinorg.cf file is time stamped today at 6:11am as 
well as all the files in /var/lib/spamassassin/3.001004. Thats assuming 
there was an update since yesterday, however, looking at my syslog it 
appears as though spamassassin did not restart.

-- 
Chris
17:37:47 up 4 days, 23:06, 1 user, load average: 0.22, 0.20, 0.19
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Any sufficiently advanced technology is indistinguishable from a rigged 
demo.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Attachment: pgpMVCnKs1jHA.pgp
Description: PGP signature

Reply via email to