Re: [leafnode-list] writeactive() not updating mtime?

[Stefan Wiens <s.wi@xxxxxxx>]

Matthias Andree <ma@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> writes:

> Joerg Dietrich <joerg@xxxxxxxxxxxx> writes:
>
>> The obvious (and for five days working without problems) solution
>> is to move updateactive(), writeactive() and unlink(lockfile) to
>> the parent.
>
> The lockfile handling is hosed and needs to be fixed in the first
> place. Don't fix the triggers, fix the problem. 

Joerg's suggestion eliminates a problem which otherwise would
unnecessarily complicate locking. I suggest fetchnews should
re-obtain the lock while doing fixxover().

Undoubtedly, this doesn't help against the error-prone locking
method.

Stefan


-- 
leafnode-list@xxxxxxxxxxxxxxxxxxxxxxxxxxxx -- mailing list for leafnode
To unsubscribe, send mail with "unsubscribe" in the subject to the list