Hello. Wath do you think about add message id to all clamav-milter log messages ? For example, curient log:
Feb 6 14:32:57 clamav-milter[4615]: clamfi_eoh Feb 6 14:32:57 clamav-milter[4615]: clamfi_envbody: 65535 bytes Feb 6 14:32:57 clamav-milter[4615]: clamfi_envbody: 33650 bytes Feb 6 14:32:57 clamav-milter[4615]: clamfi_eom Feb 6 14:32:58 clamav-milter[4615]: clamfi_eom: read stream: OK Feb 6 14:32:58 clamav-milter[4615]: i16AVKob004589: clean message from <> I think what more usable is Feb 6 14:32:57 clamav-milter[4615]: i16AVKob004589: clamfi_eoh Feb 6 14:32:57 clamav-milter[4615]: i16AVKob004589: clamfi_envbody: 65535 bytes Feb 6 14:32:57 clamav-milter[4615]: i16AVKob004589: clamfi_envbody: 33650 bytes Feb 6 14:32:57 clamav-milter[4615]: i16AVKob004589: clamfi_eom Feb 6 14:32:58 clamav-milter[4615]: i16AVKob004589: clamfi_eom: read stream: OK Feb 6 14:32:58 clamav-milter[4615]: i16AVKob004589: clean message from <> It's allow select all message log data via "grep <message id>". -- Regards, Sergey ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ Clamav-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/clamav-users
