hobbitlaunch.cfg question
list Kolbjørn Barmen
I'm wondering... the hobbitlaunch.cfg man page says.. "The key is enclosed in angle brackets, and must be unique for each task. You can choose your key-names as you like, they are only used internally in hobbitlaunch to identify each task." But what if I do have 2 keys with identical names, which one will be used? I get the impression that it's the last one, but I'm not sure. My idea is that I can leave the "original" hobbitlaunch.cfg untouched except for a "directory hobbitlaunch.d" at the end, and then override keys with files in that directory. -- Kolbjørn Barmen UNINETT Driftsenter
list Charles Goyard
▸
Kolbjørn Barmen a écrit :
My idea is that I can leave the "original" hobbitlaunch.cfg untouched except for a "directory hobbitlaunch.d" at the end, and then override keys with files in that directory.
The best thing to do is to duplicate, add DISABLED to the original, and rename yours prepended with "local". Whenever the implementation changes, your setup will still work. Avoid taking advantage of side-effects, you may end up Windowsed ;). -- Charles Goyard - user-98f9625a7a59@xymon.invalid - (+33) 1 45 38 01 31
list Buchan Milne
▸
On Tuesday 25 July 2006 13:05, Kolbjørn Barmen wrote:
My idea is that I can leave the "original" hobbitlaunch.cfg untouched except for a "directory hobbitlaunch.d" at the end, and then override keys with files in that directory.
If some kind of include-like functionality were to be implemented (and I would vote for it to be in at least hobbitlaunch.cfg and hobbitgraph.cfg), it would be better to use an include statement with globs (eg "include /etc/hobbit/hobbitlaunch.d/*.cfg) rather than a directory statement. The reason for this is to ensure that you don't unexpectedly hit a backup/swap/temporary file (or, say .rpmsave/.rpmnew). I would like to have an easier upgrade on my hobbit server with custom graph definitions, and the tasks to run that generate the data for these. Implementing something like this would make it easier for people to distribute extensions that need this (and package them etc.). Regards, Buchan -- Buchan Milne ISP Systems Specialist B.Eng,RHCE(803004789010797),LPIC-2(LPI000074592)
list Charles Goyard
▸
Buchan Milne a écrit :
If some kind of include-like functionality were to be implemented (and I would vote for it to be in at least hobbitlaunch.cfg and hobbitgraph.cfg)
It is ! All config files support the include directive. I use it for all files, so the stock setup is poked the least. For graphs, here's what I did in my local setup : /opt/hobbit/server/etc/hobbitserver.cfg defines TEST2RRD and GRAPHS, and I extend them in /opt/hobbitlocal/etc/hobbitserver.cfg : TEST2RRD="$TEST2RRD,wallbotz=ncv,reqs=ncv,template=ncv,mysql=ncv,mem_jvm=ncv,squid=ncv" GRAPHS="$GRAPHS,ncv,wallbotz,reqs,template,mysql,mem_jvm,squid" I don't like the idea of globbing filenames, but I might use it at some point. (I have 95 extensions in use at my company :)). Regards, -- Charles Goyard - user-98f9625a7a59@xymon.invalid - (+33) 1 45 38 01 31