[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [leafnode-list] lockfile_exists disaster, analysis of 1.9.19 and
Well, there is one more problem with respect to locking: the new locking
schemes (regardless whether Cornelius' suggestion or my function) CANNOT
HAND OVER THE LOCK ACROSS fork().
Clear text: the lock is lost when fetchnews forks, the child would have
to acquire the lock again. I'm currently working on a solution.
I'm wondering whether additionally fcntl locking the file would do good,
because that would adversely affect the portability. BSDs would suffer
when NFS came into play.
leafnode-list@xxxxxxxxxxxxxxxxxxxxxxxxxxxx -- mailing list for leafnode
To unsubscribe, send mail with "unsubscribe" in the subject to the list