Probably just a coincidence; I don't think anything particularly changed
with the signaling code. Did it happen more than once?
The lack of auto-clearing might be construed as a feature, considering
that segfaults and the like aren't supposed to happen and should probably
be looked at ;)
To clear, just issue a "xymon drop HOST.xymonlaunch" like any other status.
HTH,
-jc
Henrik or anyone,
I was tempted to hijack the 4.3.9 thread but held myself back.
Problem: xymonlaunch crashed on a client and the server created a
xymonlaunch column
This is the first I have seen this behavior. Was this added with 4.3.8 or
is this just a coincidence?
It would not be a big deal if I didn't have to manually drop the alert
since there is no clear or green status sent when it recovers. Again this
alert is on a client host not the server.
~David