[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kmail-devel
Subject:    Re: Bug#45545: marked as done (Mail disappears from inbox) by Carsten Burghardt <cb@magic-shop.de>
From:       Don Sanders <sanders () kde ! org>
Date:       2002-07-29 8:52:50
[Download RAW message or body]

On Monday 29 July 2002 01:17, Ingo Klöcker wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Friday 26 July 2002 23:58, Ingo Klöcker wrote:
> > On Friday 26 July 2002 09:59, Don Sanders wrote:
> > > On Tuesday 23 July 2002 07:59, Ingo Klöcker wrote:
> > > > Hmm, but in some cases we regenerate the index file. But I
> > > > don't know when. The only thing I know is that if the mail
> > > > folders are located on an NFS server and the clock of the NFS
> > > > server is ahead of the clock of the local machine then the
> > > > index is rebuild everytime the folder is selected. At least
> > > > this happened on a friend's machine.
> > >
> > > NFS is a problem. Are you able to install a test version of
> > > KMail on this friends machine to help look at NFS problems that
> > > might be introduced by being stricter about out of date
> > > indices?
> >
> > As the clock of the NFS server is now in sync with the local
> > clock this problem doesn't occur anymore on my friend's machine.
> > But I can reproduce the problem here with my two computers. The
> > index file is rebuild everytime I select the folder.
>
> I did some tests. For some reason the NFS client gives a wrong
> modification date of the index file. It seems to be the
> modification date of the local machine and not the (real)
> modification date on the NFS server's hard disk. OTOH, the
> modification date of the mbox file is always correct, i.e. equal to
> the real modification date of the mbox file on the NFS server's
> hard disk. If now the local date is behind the NFS server's date
> then the mtime of the index file is earlier then the mtime of the
> mbox file. This results in index file recreation.
>
> I tried to workaround this problem by touching the index file after
> it has been written. If I do this on the command line then the NFS
> client gives the correct mtime. But this doesn't work in KMail.
>
> Conclusion: NFS sucks!!! :-(

(silent disagreement)

> Solution for this problem: We have to store the mtime of the mbox
> file in the index file. This way the NFS server can't fool us and
> KMail.

Well um, that can't work. That would defeat the whole purpose of 
checking to see if the file was out of date.

If we did that then if someone (exited KMail and) modified the mbox 
file using an external program then the index file wouldn't be 
regenerated. This would mean the index file would be out of date and 
that could lead to mbox corruption.

Don Sanders

_______________________________________________
KMail Developers mailing list
kmail@mail.kde.org
http://mail.kde.org/mailman/listinfo/kmail
[prev in list] [next in list] [prev in thread] [next in thread]