Summary: | kmail could not lock in /var/spool/mail | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Botykai Zsolt <zsolt.botykai> |
Component: | [OLD] KDE | Assignee: | Gentoo KDE team <kde> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Botykai Zsolt
2004-02-17 21:49:09 UTC
I don't see how this is a kmail bug - if you want to use local mail like that it's your responsibility to set it up correctly, right? Aditionally there is an option in the kmail receiving option for a local mailbox to specify whether a lockfile is used and if so, where it resides. Another option (use with care on an NFS mailbox) is to use fcntl locking which basically asks the OS to do locking. This does not need access for a lockfile. Basically read the kmail manual. I think the reason is shown below (by the changed permissions), but maybe I'm wrong...: diff net-mail/mailbase/mailbase-0.00-r5.ebuild net-mail/mailbase/mailbase-0.00-r6.ebuild /usr/portage $: diff net-mail/mailbase/mailbase-0.00-r5.ebuild \ > net-mail/mailbase/mailbase-0.00-r6.ebuild ... < fperms 1777 /var/spool/mail --- > fperms 0775 /var/spool/mail 37c37 < chmod 1777 ${ROOT}/var/spool/mail --- > chmod 0775 ${ROOT}/var/spool/mail |