[EMAIL PROTECTED] wrote: > > Dave> Somebody should have already written a file lock library that > Dave> encapsulates it, so maybe we can use that. And if it doesn't > Dave> exist, it should! > > It does exist, in several flavors, as my query to python-dev indicates.
Sounds like a good addition to python, but Im not sure its the solution in this case. The cron job probably should tte using a different database filename, then atomically swap the new database in place of the old. This ensures you dont leave a partial database in place if the machine crashes/is shutdown/process is killed during the tte run. It also allows procmail to run on the old database concurrently with the training run, which I guess a lock file would prevent. Or am I confused here. Ive just re-read David's original post, and you say this the problem is caches rather than the database. Which caches are these? -- Toby Dickenson (happy procmail user) _______________________________________________ spambayes-dev mailing list spambayes-dev@python.org http://mail.python.org/mailman/listinfo/spambayes-dev
