The size of my articles.gdbm file is approaching the limit of a signed 32-bit integer:
-rw-r--r-- 1 news news 2147483413 Dec 15 11:27 articles.gdbm
This appears to be associated with an error I get while running noffle -r under strace:
29155 write(2, "gdbm fatal: lseek error.\n", 25) = 25
The first half of the bug is that there is no indication in any program output that I could see (server responses, syslogs) that this is a gdbm lseek error. I had to use strace to figure that out. If nothing else, you could make the source of this error more obvious.
The second half of the bug is that maybe its time to start using O_LARGEFILE :)
I've only been using noffle for a little while so I am not an expert by any means. I tried using noffle --expire to make the articles.gdbm file smaller and that worked, but only after a couple of iterations of making my default expire period smaller
Chris Cobb, ccobb@email.com
