I've tracked my users' email mbox corruption (see bug:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=557103 ) to this bug.
Specifically, because mlock is installed in the wrong location, there is
nothing stopping simultaneous accesses to a user's spool file.
Since this leads to data loss, I think the severity needs to be raised.
In addition, the fix (moving mlock to /usr/sbin/ where the code expects
it) seems fairly trivial.
Let me know if there's anything I can do to move this bug along.
Regards,
--Mike
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
