[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [leafnode-list] lockfile_exists disaster, analysis of 1.9.19 and
-----BEGIN PGP SIGNED MESSAGE-----
Matthias Andree <ma@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> writes:
> 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().
What happens is as soon as the parent exited, the lock will be
> 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.
Well, it's easier than I thought at first. 2.0b8 doesn't need the locks,
it just updates the .xoverinfos, 1.9.19 does, but that can be alleviated
by moving the groupinfo update to the parent, the child then no longer
needs the lock.
I have two patches that hopefully fix the locking issue. Please test.
Fix for 1.9.19:
Fix for 2.0b8: (note this slightly changes fetchnews because the new
lockfile.c does not support "silent == 0" verbose mode)
The .sig files are GPG signatures.
-----BEGIN PGP SIGNATURE-----
Comment: Processed by Mailcrypt 3.5.5, an Emacs/PGP interface
-----END PGP SIGNATURE-----
leafnode-list@xxxxxxxxxxxxxxxxxxxxxxxxxxxx -- mailing list for leafnode
To unsubscribe, send mail with "unsubscribe" in the subject to the list