Anthony, thank you very much for your response. The daemon that was reading the events froze, so apparently that was the source of the problem and your explanation fits perfectly. On Mon, Dec 28, 2009 at 12:47 PM, Anthony Minessale <anthony.minessale@gmail.com> wrote:
most likely cause would be connecting a socket then not regularly reading from it causing the buffer to fill up. any event socket connection must select on the socket and do regular read attempts or all the events will accumulate on the server side until some sanity check is reached and it begins to throw them away, the fist time there is room in this buffer again (when you consume some from the socket leaving space in the queue) it will report how many have been lost since the last read.
One way to cause this would be suspend fs_cli with ctl-z and bring it back to the foreground after some time.