[smokeping-users] Re: Multiple instances with multiple configs

[Michael McCarn]

I put all my "hosts" into separate files, then reference them using
"@include" in my main config.

I end up with etc/config for the system-wide stuff, and
etc/config.clienta, etc/config.clientb, etc/config.clientc, all
referenced in /etc/config using "@include".

If I edit etc/clienta I then need to "touch etc/config" and
"bin/smokeping --reload" to have the changes recognized.


 

-----Original Message-----
From: smokeping-users-bounce at list.ee.ethz.ch
[mailto:smokeping-users-bounce at list.ee.ethz.ch] On Behalf Of Eric
Brander
Sent: Tuesday, August 29, 2006 11:10 AM
To: smokeping-users at list.ee.ethz.ch
Subject: [smokeping-users] Multiple instances with multiple configs

Is there any negative impact to running multiple instances of smokeping
on different config files? I've found that having over 530 targets in
one config really bogs down when any changes are made to the config. So
I'm thinking of splitting it in to two or more configs and initiating
the smokeping daemon with --config=x.

Are there any pitfalls or caveats I should be aware of should I choose
to go this route?

TIA,

Eric Brander

--
Unsubscribe
mailto:smokeping-users-request at list.ee.ethz.ch?subject=unsubscribe
Help        mailto:smokeping-users-request at list.ee.ethz.ch?subject=help
Archive     http://lists.ee.ethz.ch/smokeping-users
WebAdmin    http://lists.ee.ethz.ch/lsg2.cgi

--
Unsubscribe mailto:smokeping-users-request at list.ee.ethz.ch?subject=unsubscribe
Help        mailto:smokeping-users-request at list.ee.ethz.ch?subject=help
Archive     http://lists.ee.ethz.ch/smokeping-users
WebAdmin    http://lists.ee.ethz.ch/lsg2.cgi