On 5/13/06, Theo Van Dinter <[EMAIL PROTECTED]> wrote:
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.
Sounds good.
> 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.
Was there an update available on May 8? That's when I ran sa-update last. It just happens to have been most of a week before anything else caused spamd to restart. I'm pretty sure that I got the exit code 1 from sa-update; I'm quite sure that I *didn't* get an exit code of 4 or more. I ended up with: /var/lib/spamassassin/3.001001/updates_spamassassin_org/ (empty directory) /var/lib/spamassassin/3.001001/updates_spamassassin_org.tmp/MIRRORED.BY Having removed the entire 3.001001 tree, I just re-ran sa-update and now I have what appears to be the correct update: /var/lib/spamassassin/3.001001/updates_spamassassin_org/ (lots of .cf files) /var/lib/spamassassin/3.001001/updates_spamassassin_org.cf
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.
I'm running 3.1.1.
