On Tue, Feb 15, 2005 at 03:17:00PM -0800, Justin Mason wrote:
> actually, it's not so simple.
>
> > stat64("/home/asuffield/.spamassassin/bayes_toks.expire2054", 0xbffff580) =
> > -1 ENOENT (No such file or directory)
>
> this stat is performed by SpamAssassin code;
>
> > open("/home/asuffield/.spamassassin/__db.bayes_toks.expire2054",
> > O_RDWR|O_CREAT|O_EXCL|O_LARGEFILE, 0600) = -1 EEXIST (File exists)
> > open("/home/asuffield/.spamassassin/__db.bayes_toks.expire2054",
> > O_RDWR|O_CREAT|O_EXCL|O_LARGEFILE, 0600) = -1 EEXIST (File exists)
> > open("/home/asuffield/.spamassassin/__db.bayes_toks.expire2054",
> > O_RDWR|O_CREAT|O_EXCL|O_LARGEFILE, 0600) = -1 EEXIST (File exists)
>
> this open is being performed "under the covers" in libdb. We have no
> control over this, as far as I know, since it's all hidden underneath
> DB_File.Oh, fair chance that it just doesn't like being fed an O_EXCL then. That'll be the libdb backup file. > I didn't think we used that functionality (journalling, if I recall > correctly). We could delete the "__db.bayes_toks*" files in advance, if > that would help? but still, mysterious. > > what versions of libdb and the perl DB_File module are you using? and what > version of SpamAssassin? ii perl 5.8.4-6 Larry Wall's Practical Extraction and Report Languag ii spamassassin 3.0.2-1 Perl-based spam filter using text analysis ii libdb4.2 4.2.52-18 Berkeley v4.2 Database Libraries [runtime] Those should be all the relevant ones. Happens to be DB_File 1.808. -- .''`. ** Debian GNU/Linux ** | Andrew Suffield : :' : http://www.debian.org/ | `. `' | `- -><- |
signature.asc
Description: Digital signature
