Updated by mfriedrich on 2011-03-14 21:33:42 +00:00

you'd have to keep track of different configs etc. and then search which version the user might have installed. that's more headache than everything else.

i'd rather let that an option in rpms (config no replace) or debs than in in plain source code. people using source install should reconsider using packages instead.

if you really want to, we can create smaller config samples which describe the version changes (new config options in 1.4 in 1.5 etc). people then need to copy that themselves.

which then would be great if we could have a conf.d (which gets defined in main icinga.cfg) and the core reads all added configs from that directory)

the initial idea sources from the event broker module line to be added automagically, but the main problem is that the core and cgis read the config at several places - this needs to be combined/reworked.

please refer to #162

(me thinks this would be great)

Updated by mfriedrich on 2011-05-05 16:47:05 +00:00

• Status changed from New to Feedback
• Target Version deleted 1.5

Updated by mfriedrich on 2011-05-19 08:53:01 +00:00

• Status changed from Feedback to Closed

i'd suggest adding a docs or wiki page where we frequently put new cfg options, if any. doing this by software would lead into overkill.