Mike Peeler <zconcept(_at_)panix(_dot_)com> writes:
Jeff Orrok <jeff(_at_)rt(_dot_)com> wrote:
Ah, the joys of sheer stupidity.
I don't necessarily succeed, but I try not to go around calling things
stupid unless I'm pretty sure who's on top, me or it.
Well, you certainly didn't succeed at comprehending that I was calling my
own actions stupid.
Procmail's internal lockit() function (not lockfile) creates a temp in
its usual safe way, and renames this temp to be the desired lock-file.
The tempfile couldn't be created, so lockit() waits locksleep seconds,
and tries again, for a total of nfsTRY (eight) times. The unique-name
generator intentionally rotates one character of the filename from one
try to the next, in hopes of finding an empty slot in the hash bucket.
The observed behavior was not the result of any inadvertent data space
corruption, nor is it a design flaw.
If you say so. Since ".nixon.xkey.com" has nothing to do with the name of the
lockfile, I thought that it was overwriting some other part of memory. And
still, there is no point in retrying something that destined to fail: creating
files in non-existent directories.
Jeff
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail