On 1/30/06, Csaba Henk <csaba-ml@creo.hu> wrote:
On 2006-01-30, <belontzu@gmail.com> <belontzu@gmail.com> wrote:
> I have an unusual behaviour with mutt_dotlock.
>   mutt_dotlock file => fail
> and
>   strace mutt_dotlock file => succed

Isn't mutt_dotlock setuid?
Did you try "-o allow_root" ?

You are right. Using "-o allow_root" or removing setuid bit on mutt_dotlock worked.

But, why it's working with fuse 2.2.1?
It's there a way to tell fuse to use both ids, real and effective?
Or something else?