On Sat, May 13, 2006 at 04:27:14PM -0700, Bart Schaefer wrote: > But surely there's some kind of disconnect here. sa-update creates an > empty directory that spamassassin (and spamd) then uses preferentially > to the one that really has the rules in it.
It's not empty if the download is successful. I believe there's a ticket about changing the behavior so an empty directory isn't left behind if the first attempt to do an update fails. > In that case I would argue that either (a) running sa-update should > not create a directory when there are no updates to populate it, or I'd have to double check, but for (a), I believe that happens already. Having no updates available doesn't create the directory. However, what's more likely is that there's an upgrade available but the download failed. > (I didn't bother to restart spamassassin after I ran it, because it > reported there were no updates available) and goes on to say: [...] > Nowhere does it say that it creates this directory and leaves it empty > when there are no updated rules. Nowhere in "man sa-update" does it > say that either. How was I supposed to realize that running sa-update > would leave me with a crippled installation? So I'm confused. If you're running 3.1.0, sa-update acts completely differently and there are no updates available for it anyway. If you're running 3.1.1, there are updates available. If you're running 3.2.0, there are updates available. So the only thing that makes sense here is that the download failed, which is documented in the wiki page. -- Randomly Generated Tagline: To err is human, To purr feline. -- Robert Byrne
pgpZuhE5v2KgB.pgp
Description: PGP signature