This bug was fixed in the package xymon - 4.3.17-4
---
xymon (4.3.17-4) unstable; urgency=medium
* Add debconf question to disable the automatic migration from hobbit to
xymon. (hobbit-client/automatic-xymon-migration; default true)
-- Christoph Berg Thu, 23 Oct 2014
14:31:
** Branch linked: lp:debian/xymon
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/401393
Title:
Warn if clientlaunch.d file name requirements are not met
To manage notifications about this bug go to:
** Changed in: xymon (Ubuntu)
Status: Opinion => Fix Committed
** Changed in: xymon (Ubuntu)
Assignee: (unassigned) => Axel Beckert (xtaran)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/4
Hi Arie,
Arie Skliarouk wrote:
> Ok, what about providing /etc/xymon/clientlaunch.d/README file with following
> content:
> -
> The directory is the place for custom configuration that will not be affected
> on xymon upgrade.
That's not really true.
Myabe you meant:
Ok, what about providing /etc/xymon/clientlaunch.d/README file with following
content:
-
The directory is the place for custom configuration that will not be affected
on xymon upgrade.
The files must have .cfg extension.
-
--
You received this bug
> Xymon, by its CLI nature, is already hard to configure. Please don't
make it harder than it already is.
Huh? On of the things I like with Xymon is that you don't have to
configure so many things so verbosely as you need to do that Nagios even
only reports a single thing. Just one line per host a
Why not? If that can save time for someone, I don't mind having couple
of warning messages in syslog for each hobbit start.
Better alternative would be to write xymon_conf_check program that will
check configuration files for correctness and show list of files it used
(or for some reason - did not
We cannot warn on random files there because there will always be files
named foo~, foo.backup.1, foo.dpkg-old, foo.cfsaved, and whatever stuff
editors and config management software comes up with.
It might be possible to warn on files that do not have any dots in the
name, though. (or maybe do no
** Summary changed:
- declarations in clientlaunch.d directory are disregarded
+ Warn if clientlaunch.d file name requirements are not met
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/401393
Title:
