Warn if clientlaunch.d file name requirements are not met

Did you restart the daemon? It doesn't reliably load new files on reload.

Yes, I did restart the daemon:
/etc/init.d/hobbit-client start
/etc/init.d/hobbit-client stop

Here is the content of the file I have put into /etc/hobbit/clientlaunch.d directory.
[raid]
    #DISABLED
    ENVFILE $HOBBITCLIENTHOME/etc/hobbitclient.cfg
    CMD $HOBBITCLIENTHOME/ext/bb-raid.pl
    LOGFILE $HOBBITCLIENTHOME/logs/hobbitclient.log
    INTERVAL 10m

Did you include a ".cfg" extension in the filename in the clientlauch.d directory? It needs to have one, because the Debian version needs a filter one filenames so that it doesn't read .dpkg-old and friends.

That was the problem. Once I renamed the file to have .cfg extension it was automatically picked up.

Can you make hobbit-client to print warning into log files on start in case it finds filenames in directory etc/hobbit/clientlaunch.d that do not have .cfg extension? This might have save time for someone like me in the future.

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 not match *.cfg*)

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).

Xymon, by its CLI nature, is already hard to configure. Please don't make it harder than it already is.

> 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 and most stuff works out of the box.

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.
-------------------------

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:

   In this directory, xymon client extensions can place their
   configuration files. Manually added configuration files may not be
   handled automatically on package upgrades.

> The files must have .cfg extension.

Will add that one for sure.

  Regards, Axel
--
 ,''`. | Axel Beckert <email address hidden>, http://people.debian.org/~abe/
: :' : | Debian Developer, ftp.ch.debian.org Admin
`. `' | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
  `- | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5

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 <email address hidden> Thu, 23 Oct 2014 14:31:57 +0200