Re: Antonio Radici 2009-01-25 <497cc249.5030...@dyne.org>
> first of all, I was able to reproduce the problem but with a different
> outcome:
> lockd took all the CPU and I had to reboot my system.
>
> cfsd is running over NFS and it would be interesting to know which kernel
> you're using and if
Hi,
first of all, I was able to reproduce the problem but with a different outcome:
lockd took all the CPU and I had to reboot my system.
cfsd is running over NFS and it would be interesting to know which kernel
you're using and if you still see the problem. I think that this is outside
the mutt
Dear Christoph,
I ran mutt with strace, and obtained the following (see below). The lock
failure seems to be related to fctrl coming up with a stale NFS handle (near
the end of the strace output). I don't know why it thinks so, but the
information on the encrypted filesystem is fully available
Dear Christoph Berg, you wrote:
> Hi Frank,
>
> do you still experience the locking problem with recent mutt packages?
I'm afraid I do. My current version is Version: 1.5.13-1.1
I also think your request to use strace slipped my attention, so far. I'll do
it one of these days and let you know wh
Hi Frank,
do you still experience the locking problem with recent mutt packages?
Re: Frank B. Brokken 2006-01-30 <[EMAIL PROTECTED]>
> > > > > I find it very surprising that mutt_dotlock from the command line
> > > > > works, and it does not from within mutt.
>
> I'm afraid not. I just tried
Dear Adeodato Sim??, you wrote:
> Hi, any updates on this? Thanks.
>
> * Adeodato Sim?? [Mon, 21 Nov 2005 19:50:52 +0100]:
>
> > * Frank B. Brokken [Mon, 31 Oct 2005 20:59:27 +0100]:
>
> > Hi,
>
> > (Sorry for the delay.)
>
> > > > I find it very surprising that mutt_dotlock from the comma
Hi, any updates on this? Thanks.
* Adeodato Simó [Mon, 21 Nov 2005 19:50:52 +0100]:
> * Frank B. Brokken [Mon, 31 Oct 2005 20:59:27 +0100]:
> Hi,
> (Sorry for the delay.)
> > > I find it very surprising that mutt_dotlock from the command line
> > > works, and it does not from within mutt
* Frank B. Brokken [Mon, 31 Oct 2005 20:59:27 +0100]:
Hi,
(Sorry for the delay.)
> > I find it very surprising that mutt_dotlock from the command line
> > works, and it does not from within mutt.
> I agree. But I tried to save a mailmessage (i.e., append) from my incoming
> mailbox (i.e.,
Dear Adeodato Sim??, you wrote:
> Uhm. Let's imagine your mailbox is MAILBOX=/path/to/mailbox. What's
> the output of:
>
> % ls -ld `dirname $MAILBOX`
> % touch `dirname $MAILBOX`/foo
> % /usr/bin/mutt_dotlock -p $MAILBOX || echo failure
> % ls -l ${MAILBOX}.lock
Ok, here we
* Frank B. Brokken [Mon, 31 Oct 2005 10:35:10 +0100]:
> and when I run mutt_dotlock from the command line to lock the file its
> return values are 0, both for locking and unlocking. So, I get the impression
> that locking is possible, but that mutt somhow is unable to lock. The mail
> file has
Package: mutt
Version: 1.5.9-2
Severity: normal
Dear maintainer,
I use the cfs Cryptographic Filesystem to store files holding confidential
information in. Some of these files contain mail, and mutt should be able to
read and modify these files. Mutt has no problem reading those files, but i
11 matches
Mail list logo
