> Actually my report was NOT about this limitation. You have it - it is fine.
> The problem is that I add some 'zombies' or dead files to my logbook.
> 
> BTW is there a tool to check the 'integrity' of a logbook? That all
> attachments are in place,  there are no dead files, etc. I perfectly
> understand that it is not _highly_ desired or needed, but with the two last
> problems (auto-removing of attached files and silent adding a new ones with
> 20+ attachments) I have doubts that our logbook in a good state. And we 
just
> started to use it. And I am still so excited about it!!

Actually my philosophy is not to cure symptoms of a problem, but fix the 
source of it. The reply/attachment bug is fixed, and a warning about 
exceeding the number of attachments will come soon.

About the integrity, there is no problem. As you might know, the xxxxxxa.log 
files are plain text files. The line "Attachments: xxx" contains a simple 
text list of all attachments. In the above case a few files might be missing 
in that line, but they are present in the log directory. So in worst case 
edit the xxxxxxa.log file manually, adding the file names, and maybe restart 
elogd to rebuild the index properly. Otherwise there is no integrity problem.