On Thu, Mar 15, 2012 at 10:29 AM, Sorrell, Al <span dir="ltr"><<a href="mailto:Al_Sorrell@troweprice.com">Al_Sorrell@troweprice.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Toby,<br>
<br>
First off, thanks for continuing to evolve this great software! Let me explain what I'm looking for...<br>
<br>
I have several systems which are all polling the same set of devices; one is our primary system, one is at our DR site, and one is being setup now to eventually replace our current primary. The config file for each is *almost* identical.<br>
<br>
Specifically the *** General ** section needs to be different in order to specify the correct server in the cgiurl= section; potentially, others might have different paths for the various directories, though that's not a problem for me.<br>
<br>
What I'd like to see would be something like an<br>
Include /path-to-file<br>
<br>
That way, I could have my $SMOKEPING/etc/config with statements like:<br>
========================<br>
*** General ***<br>
owner=...<br>
contact=...<br>
imgurl=...<br>
cgiurl=<a href="http://myserver/." target="_blank">http://myserver/.</a>..<br>
<br>
Include $SMOKEPING/etc/common_config<br>
<br>
========================<br>
<br>
Where $SMOKEPING/etc/common_config would have everything which isn't system-specific.<br>
<br>
This would certainly make it much easier to keep multiple systems in sync without the need to use 'sed' prior to copying configs between systems.<br></blockquote><div><br></div><div><div>SmokePing certainly supports @includes - see <a href="http://oss.oetiker.ch/smokeping/doc/smokeping_config.en.html#IGENERAL_SYNTAX">http://oss.oetiker.ch/smokeping/doc/smokeping_config.en.html#IGENERAL_SYNTAX</a></div>
<div><br></div><div>I use this feature to break my target configs into logical chunks, even using nested @includes. I believe you could do it as you suggest above, with the main config differentiated; another alternative, and depending on how you manage your distributed configs, is to keep the main config the same, with the variable items pulled in via @includes. Six of one...</div>
<div><br></div><div>Cheers,</div><div><br></div><div>-tt</div><div><br></div><div><br></div></div><div><br></div></div>