Prints out garbage when host variables are used
Bug #1193115 reported by
Stephen Frost
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nagcon (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
If a host variable is defined, it shows up in the status.dat file and when nagcon tries to process it, it can't find it in the fixed array of known variables and instead it spits out the entry with "[VARIABLE] ???" (search for the only set of three question marks in the package, you'll find it...).
Simple answer is for nagcon to, instead, ignore these custom variables. Patch included to remove the stupid printf().
After that, it works great.
Thanks!
Stephen
To post a comment you must log in.
The attachment "Nuke stupid printf()" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team.
[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.]