f course it works now ;-) I think I'd been making changes to xymonserver.cfg without restarting xymon. Sorry for the bother...
cheers, Phil
On 25/08/2011 at 3:45 PM, in message <4E55E171.9020202 at hswn.dk>, Henrik Størner wrote: On 25-08-2011 05:07, Phil Crooker wrote: I was having an issue with BBWin client messages being too large and getting truncated. In the xymonserver.cfg help file, eg:
"MAXMSG_STATUS The maximum size of a "status" message in kB, default: 256. "
I tried putting that variable in and enlarging it to 512 but still received the same error and no change to MAXMSG either. I found I had to use a value in bytes, not KB as stated - this was reported back in 2006:
And I belive it was fixed back then. I just tried it with 4.3.4, and it picks up the KB-value just fine. What version are you running?
4.3.4. As it works for you, I'll do some homework and report back.
You can use the command "ipcs -m" to see the size of the shared memory segments that Xymon uses (you must be logged in as root, or the xymon user).
I also found I had to restart xymon for it to pick up the changes. It may be possible to just kill -HUP or something, I didn't try. But I didn't expect this behaviour as the other config changes I've made have been picked up on the fly...
Changing xymonserver.cfg usually requires a restart. All other config
changes are picked up automatically.
Could that please be included in the xymonserver.cfg man page?
thanks, Phil
Regards, Henrik
Xymon mailing list Xymon at xymon.com http://lists.xymon.com/mailman/listinfo/xymon
Xymon mailing list Xymon at xymon.com http://lists.xymon.com/mailman/listinfo/xymon
participants (1)
-
Phil.Crooker＠orix.com.au