[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Added ~/.<program>rc as a config file.

From: Sam Roberts
Subject: Re: Added ~/.<program>rc as a config file.
Date: Thu, 21 Mar 2002 23:45:07 -0500
User-agent: Mutt/1.3.16i

Quoteing address@hidden, on Thu, Mar 21, 2002 at 12:40:47PM +0200:
> Changing the topic, there is a problem with locking mechanism
> (locker.c): if the mailbox lives in a non-writable directory
> the locking will fail (and that is correct). But along with
> it the scanning of the mailbox will also fail, e.g. in mbox_scan0:
>   if((status = locker_lock (mailbox->locker)))
>     {
>       monitor_unlock (mailbox->monitor);
>       return status;
>     }
> Thus it effectively disables imap4d's 'other' namespace, which in most
> cases is located in a non-writable directory. Disabling the locking
> in this case doesn't seem to be correct, since the mailbox itself may
> still be writable. How about using a separate directory for lock
> files, like /var/lock found on most systems?

I don't know anything about the other namespace, particularly. What's
the setup?

My spool was writeable only by group mail, I had to change that to
use mailutils to open my spool file. I want to add a flag to the
locker that will cause the locker to behave the same, but call dotlock 
instead of doing the locking itself. dotlock can be setgid mail,
or setuid root, and it will lock the file even in a directory the
user doesn't have write permission to (after appropriate permissions

Will this address the problem you're talking about?


Sam Roberts <address@hidden> (Vivez sans temps mort!)

reply via email to

[Prev in Thread] Current Thread [Next in Thread]