2 Apr
2010
2 Apr
'10
12:21 p.m.
On Apr 01, 2010 at 18:56, Henning Westerholt <henning.westerholt(a)1und1.de> wrote:
On Wednesday 24 March 2010, marius zbihlei wrote:
I think it's a good idea, but you probably mean sercmd and not serctl.
serctl is the old obsolete fifo based ser administration tool.
To further increase confusion ser_ctl is the current ser administration
tool :-)
It might be a good idea to have a look at ser_ctl too. It uses XML-RPC
to communicate (it duplicates sercmd functionality, but AFAIK without
the interactive tab-completion and history mode) and it can handle all
the other DB based management stuff (add users, ACLs a.s.o.). It's
written in python and it should be easily extensible to handle kamailio
DB format (so it has the potential of being the universal SR management
tool, switching DB modes based, for example on a conf value).
Unfortunately it lived in the same CVS repository as ser, but in a
separate directory (which was not imported in sip-router), making it
close to invisible.
More information:
http://git.sip-router.org/cgi-bin/gitweb.cgi?p=ser;a=blob;f=ser_ctl/README;…
http://lists.iptel.org/pipermail/serusers/2007-January/031869.html
Repository:
http://cvs.berlios.de/cgi-bin/viewvc.cgi/ser/serctl/
http://git.sip-router.org/cgi-bin/gitweb.cgi?p=ser;a=tree;f=ser_ctl;hb=HEAD
Andrei
As kamailio and ser get more and more unified,
sharing common modules
and core, one of the last remaining points is the intermixed usage of
kamctl and sercmd to setup specific parameters. One example is the cfg
framework changes (from ser) that Kamailio 3.1.0 will bring, that will
require the use of "sercmd" on setting specific module config params.
The issue is that the documentation also references the "kamctl" utility
to specify reload actions etc.
What I suggest is that we strip kamctl with its fifo capabilities and
leave it only with DB, ACL management and such(that sercmd doesn't
provide), and use only sercmd on examples in the documentation files.
This will require no changes to code (well some features from kamctl
will be deprecated), but only documentation changes. This will ensure
that documentation is kept well organized and coherent across modules.
[..]
Hello,
any other opinions on this proposal? No oposition agaisnt the removal of the
common functionality in kamctl and promoting of serctl as the main server
control tool?