On Jun 23, 2009 at 10:07, Klaus Darilion <
[hidden email]> wrote:
That's great, I'll try to verify it.
The biggest problem would be how to keep it in sync.
We should also mark the options that can be changed after start-up, at
runtime.
For example a lot of the core options can be changed at runtime, either
using core as the config group, or the transport (tcp or sctp).
E.g.:
debug -> sercmd cfg.set_now_int core debug 5
tcp_connect_timeout -> sercmd cfg.set_now_int tcp connect_timeout 2
udp_mtu -> sercmd cfg.set_now_int core udp_mtu 1300
One way to see all the options acessible using the cfg framework and
defined in the core is to start sr, loading the cfg_rpc and ctl modules
and then run:
sercmd cfg.list | egrep "core|tcp|sctp"
but note that not all the options can be changed, some are read-only.
sercmd cfg.help <group> <option> might help
(e.g. sercmd cfg.help core udp_mtu).
NEWS should help too (at least all the new options added that can be
changed at runtime are "marked").
Andrei
_______________________________________________
sr-dev mailing list
[hidden email]
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev