I understand that it isn't a xymonnet test, and that protocols.cfg shouldn't play into it. My hypothesis was that nopropyellow was taking its list of legit targets from those found in protocols.cfg. Not that xymonnet was somehow in play.
Does it misbehave with nopropred, or only with nopropyellow?
--
Do things because you should, not just because you can.
John Thurston XXX-XXX-XXXX
user-ce4d79d99bab@xymon.invalid
Department of Administration
State of Alaska
On 9/18/2018 4:51 PM, Dave "doughnut" Fogarty wrote:Well, "mycustomtest" is actually "chksum" and it's not a network test, so protocols.cfg is not going to help.
Since I can use "chksum" to accurately select it with xymondboard, I am sure I have a valid name to that point. The NOPROPYELLOW is the only place having issues.