Summary: | uw-imap should be configured to use proper file locking | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Danek Duvall <duvall> |
Component: | Current packages | Assignee: | Net-Mail Packages <net-mail+disabled> |
Status: | RESOLVED WONTFIX | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Danek Duvall
2005-03-16 10:30:23 UTC
Try comment #8 from https://bugzilla.redhat.com/beta/show_bug.cgi?id=103479 Thats the workaround we are going to adopt. Cheers, Ferdy Why that workaround? As a system distributor, you get to patch things so they work properly out of the box, without config files, which should generally only be used for overriding system-default (not program-default) behavior. In addition, the locking mechanism used by all the mail programs gentoo supports needs to be coordinated, or the user may very well end up with coordinated mailboxes. My system has postfix, pine, uw-imap, procmail, and mutt, which use fcntl, flock, flock, dotlock, and fcntl/dotlock, as best I can tell. It's not a heavily used system, so I've gotten lucky so far, but it's a recipe for disaster on a heavier system. Gentoo's mail programs all need to be configured to use the same locking mechanism(s), so that we don't end up with corrupt mailboxes. Just eliminating warnings (even as bogus as they are) doesn't solve anything except slightly larger logs .... Well, if you can provide _reliable_ patches for all relevant packages to use single filelocking mechanism, I see no problem with this. Since mailbase doesn't enforce perms anymore, this is something I don't think we'll fix. (unless said patches are sent). Cheers, Ferdy |