October 25, 2019 5:42 PM, "Chris Green" <c...@isbd.net> wrote:
> Even more information!
>
> mutt_dotlock is failing when I try and lock the file across the
> sshfs file system:-
>
> chris@t470$ mutt_dotlock /home/chris/Mail/folder/test/fred
> chris@t470$ echo $?
> 1
> chris@t470$
>
> (The folder Mail is an sshfs mount)
>
> There is no permission problem for me to create files:-
>
> chris@t470$ ls -al /home/chris/Mail/folder/test
> total 8
> drwxrwxr-x 1 chris chris 4096 Oct 25 10:38 .
> drwxrwxr-x 1 chris chris 4096 Oct 25 10:35 ..
> -rw-rw-r-- 1 chris chris 0 Oct 25 10:25 fred
> chris@t470$ touch /home/chris/Mail/folder/test/fred.lock
> chris@t470$ ls -al /home/chris/Mail/folder/test
> total 8
> drwxrwxr-x 1 chris chris 4096 Oct 25 10:40 .
> drwxrwxr-x 1 chris chris 4096 Oct 25 10:35 ..
> -rw-rw-r-- 1 chris chris 0 Oct 25 10:25 fred
> -rw-rw-r-- 1 chris chris 0 Oct 25 10:40 fred.lock
> `
> So how do I diagnose what the actual error is? Is mutt_dotlock trying
> to run as 'mail' rather than 'chris'?
I wonder if strace(1) could help you
('Cause it was suggested for finding Why Evince couldn't read files like
~/.mutt/file.pdf in this mailing list.)
--
旋转少女
