Minor Description
Messages output by the syslog appender appear to have a null appended to the output text. Log4j does not do this.
If using a free syslog daemon such as Kiwi, the syslog messages sent by log4cxx will always have the suffix "<000>", whereas the log4j messages do not.
Sample log4j syslog tcp/ip packet:
0000 00 18 8b d0 9c 46 00 e0 52 d1 60 00 08 00 45 00 .....F..R.`...E.
0010 00 38 00 00 40 00 3d 11 bb b5 8a 78 d7 3a 8a 78 .8..@.=....x.:.x
0020 95 d4 81 a3 02 02 00 24 34 92 3c 31 32 3e 55 73 .......$4.<12>Us
0030 65 72 20 27 61 64 6d 69 6e 27 20 6c 6f 67 67 65 er 'admin' logge
0040 64 20 6f 75 74 2e d out.
Sample log4cxx syslog tcp/ip packet:
0000 00 18 8b d0 9c 46 00 e0 52 d1 60 00 08 00 45 00 .....F..R.`...E.
0010 00 5b 00 00 40 00 3d 11 bb 92 8a 78 d7 3a 8a 78 .[..@.=....x.:.x
0020 95 d4 81 a4 02 02 00 47 18 d1 3c 31 32 3e 43 6f .......G..<12>Co
0030 6e 63 75 72 72 65 6e 74 20 73 65 73 73 69 6f 6e ncurrent session
0040 20 6c 69 6d 69 74 20 72 65 61 63 68 65 64 2e 20 limit reached.
0050 54 72 61 6e 73 61 63 74 69 6f 6e 20 69 73 20 72 Transaction is r
0060 65 6a 65 63 74 65 64 2e 00 ejected..
Note the last byte of '00' that appears in the log4cxx packet but not the log4j packet.