Re: dotlocking causes problems when fchdir() fails

1999-06-10 Thread Thomas Roessler
On 1999-06-10 18:54:43 +0100, Lars Hecking wrote: > The man page continues to say > Applications which use this system > call must be coded to detect this failure and switch to > using chdir() from that point on. > which might be important for fixing this. Using chdir() t

Re: dotlocking causes problems when fchdir() fails

1999-06-10 Thread Lars Hecking
> (*--For what it's worth, the man page says, "fchdir() is > provided as a performance enhancement and is guaranteed to fail > under certain conditions.") The man page continues to say Applications which use this system call must be coded to detect this failure and switch to

dotlocking causes problems when fchdir() fails

1999-06-10 Thread Paul Kimoto
I am running mutt 0.95.{5,6}i on SunOS 4.1.4. It appears that fchdir() often fails [*], and so the current directory is not restored after it's changed by dotlock_invoke() in dotlock.c. This causes nonsensical error messages when doing something like "mutt -f ../../maildirectory/mailbox" (t