[Kde-pim] mbox + fileChanged slot

Martin Koller kollix at aon.at
Mon Feb 3 21:39:10 GMT 2014


Since recently I often get an informational message that akonadi detected
that the mbox file was changed by an external program - 
which is exactly what I want and do: an external program downloads mails and
appends them to an mbox file.
The message from the mbox resource says "...To prevent this from happening "
                      "use locking and make sure that all programs accessing the mbox "
                      "use the same locking method."
but this is what my external program already does.
What I do not grasp in the code of the mboxresource (SingleFileResourceBase) is:
The method SingleFileResourceBase::fileChanged(), which is triggered by the filewatcher,
is ALWAYS calling handleHashChange(); (which emits this warning message).
I don't see how locking could change that.

What was the plan to make this work without the warning message ?

On the other side, when I try to force that behavior by
cat someMailFile >> ~/mbox
I do not get that warning message ...
Is the emitted warning message not always forwarded to KDE's notification system?

P.S.:KDE 4.12.1, openSuse
-- 
Best regards/Schöne Grüße

Martin
A: Because it breaks the logical sequence of discussion
Q: Why is top posting bad?

()  ascii ribbon campaign - against html e-mail 
/\  www.asciiribbon.org   - against proprietary attachments

Geschenkideen, Accessoires, Seifen, Kulinarisches: www.bibibest.at
_______________________________________________
KDE PIM mailing list kde-pim at kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
KDE PIM home page at http://pim.kde.org/



More information about the kde-pim mailing list