It's not the memory management, it's the file management that is the
problem. Yarn uses several overview files to keep track of the news
database, and two instances could be updating this file at the same
time, which corrupts it.
Of course it would be possible to adapt Yarn so that it could work
around this (lockfiles, flock() and cousins, etc) but right now it
simply doesn't do that.
--
\/ Arnoud "Galactus" Engelfriet - galactus@stack.nl This space
5th year Business & Computing Science student left blank
URL: http://www.stack.nl/~galactus/ PGP: 0x461A1A35 intentionally.