Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
It is somehow expected that when one does own custom installation may have to tune it properly in many places.
Surely, i understand that. This specific script kamctl offers an easy way to accomplish that by searching some standard paths it may find the kamctlrc. Maybe we can document, that it searches all the paths and uses all of the config files found and in which order.
I said that your PR breaks existing behaviour
Yes, unfortunately, this breaks the existing behaviour of users and completely understand that. If we can't find a way to preserve the previous behaviour. We can close this altogether.
Then, likely a typo of yours, but
/etc/kamailio/kamctlrcinstead of/etc/kamailio/kamctlis the expected base config file for kamctl, being the one deployed with package-based installation -- just for sake of clarity.
True that was a type. I meant /etc/kamailio/kamctlrc.
To your 2., can you point where {install_prefix}/sbin/kamctlrc is taken as base config?
I based the above finding on these lines. https://github.com/kamailio/kamailio/blob/18b23187dd89e3b36c0dd95d4796484bef3d2e62/utils/kamctl/kamctl#L22C1-L39C3
The first path that is searched and used (sourced) is the kamctlrc found in the same folder as kamctl that runs (either in the standard location or not). As you can see in my description of this pr,
# Running {install_prefix}/sbin/kamctl (before changes in order) it prints :
Loading config file /home/xenofon/kamailio-source-install/sbin/kamctlrc
Loading config file /etc/kamailio/kamctlrc
Loading config file /home/xenofon/kamailio-source-install/etc/kamailio//kamctlrc
SIP_DOMAIN env var is kam0.XXXX.net
DBENGINE env var is MYSQL
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.