I don't think that wholistic centralized management is an acceptable option.
Even with centralized management smsbox-id will be required. There are
several features that are only applicable to the particular instance you
need them. For example, live reconfiguration of services or sendsms accounts
Besides, in a distributed administration system, the easiest thing is to
have a custom page with links to each system, therefore, so that everything
is managed from a centralized URL.
BR,
Nikos
On Sat, Dec 18, 2010 at 7:34 PM, Nikos Balkanas nbalka...@gmail.com wrote:
No, it won't.
Well, it's the way most clustered applications are usually managed: from a
central place and a set of agents on each node.
In kannel's case, it doesn't need to be bearerbox itself, but the cluster
instances are not usually managed from a scattered set of urls, it would be a
nightmare to
Sure, go maintain it yourself manually on a set of thousands of nodes.
The easiest thing is to let the _system_ keep track of its registered resources
and provide you with that list.
Go check how most clustered systems work, I bet you won't find many requiring
the administrator to create a
Wow, well this was fun and productive. I guess I should be happy I've at
least created a feature that I can use, and sparked some really
fun-to-listen-in-on bickering.
I can't find the portion in the code where bearerbox actually sends a signal
to smsbox anyway (from the best I can figure out
OS:
Linux 2.6.18-194.26.1.el5 #1 SMP Tue Nov 9 12:54:20 EST 2010 x86_64 x86_64
x86_64 GNU/Linux
Kannel version:
1.4.3 stable release
compile options:
--disable-localtime --with-malloc=native --with-mysql
--with-mysql-dir=/usr/lib64/mysql/
Dear Kannelers
smsbox was crashed suddenly with the
