|
I have a suspicion it may be related to Unicode issues.
The NagEvLog package does not (yet) support unicode, due to limitations in the old compiler I have, and the extensive use of strings as byte-arrays (you need ot use unicode functions everywhere and cant code your own char * stuff any more).
Unicode can contain characters which the normal string processing functions take as an end-of-string delimiter. This is probably what's going on; there may be embedded unicode in the string (first case) and it may be hitting the character limit for NSCA (second case).
Note that the latest NSCA and Nagios support much longer messages, so NagEvLog could be recompiled with a higher limit though this would possibly damage backwards compatibility.
_________________
Steve Shipway
UNIX Systems, ITSS, University of Auckland, NZ
Woe unto them that rise up early in the morning... -- Isaiah 5:11
|
Login
Register
FAQ
Members
