The following group of messages are causing a lot of noise in the mongod logs (it displays over and over).

I tested the same code with an older version of the driver and it didn't display these messages in the mongod log.

------------------------- mongoniff:

query:

{ cid: ObjectId('4d1b6314e528c81a1f200e03') }

ntoreturn: 0 ntoskip: 0 127.0.0.1:27017 <<-- 127.0.0.1:52976 1766 bytes id:581d98b8 1478334648 - 3700

reply n:10 cursorId: 0

{ _id: "Rnz4c.local-f65b47db16df8f14d7e5aec03a308614-4d1b6314e528c81a1f200e03", adr: "0:0:0:0:0:0:0:1%0", ahn: "Rnz4c.local", cid: ObjectId('4d1b6314e528c81a1f200e03'), lu: 1300932926583, p: false, uc: 150 }

127.0.0.1:52976 -->> 127.0.0.1:27017 32 bytes id:e75 3701 killCursors n: 1

------------------------- mongod log:

killcursors: found 0 of 1
Wed Mar 23 23:28:58 [conn25] killcursors: found 0 of 1
Wed Mar 23 23:28:59 [conn25] killcursors: found 0 of 1
Wed Mar 23 23:29:03 [conn25] killcursors: found 0 of 1
Wed Mar 23 23:29:04 [conn25] killcursors: found 0 of 1
Wed Mar 23 23:29:08 [conn25] killcursors: found 0 of 1
Wed Mar 23 23:29:09 [conn25] killcursors: found 0 of 1
Wed Mar 23 23:29:13 [conn25] killcursors: found 0 of 1
Wed Mar 23 23:29:14 [conn25] killcursors: found 0 of 1
Wed Mar 23 23:29:18 [conn25] killcursors: found 0 of 1
Wed Mar 23 23:29:19 [conn25] killcursors: found 0 of 1
Wed Mar 23 23:29:23 [conn25] killcursors: found 0 of 1
Wed Mar 23 23:29:24 [conn25] killcursors: found 0 of 1
Wed Mar 23 23:29:28 [conn25] killcursors: found 0 of 1
Wed Mar 23 23:29:29 [conn25] killcursors: found 0 of 1
Wed Mar 23 23:29:33 [conn25] ClientCursor::find(): cursor not found in map 0 (ok after a drop)