@xkaraman: usually the applications are designed to work with standard installation from a package or source tree. That's what kamctl tries to look after as well. It is somehow expected that when one does own custom installation may have to tune it properly in many places.

I am not against improving things of about how is done now, I said that your PR breaks existing behaviour, which is common to other pieces of linux software, but also used as it is for many years.

Then, likely a typo of yours, but /etc/kamailio/kamctlrc instead of /etc/kamailio/kamctl is the expected base config file for kamctl, being the one deployed with package-based installation -- just for sake of clarity.

To your point 1. I somehow responded above, at least partially -- now how many files one app looks for and loads is probably specific to it, I wanted to highlight that sourcing many files is not uncommon. If you want to elaborate more I can do it.

To your 2., can you point where {install_prefix}/sbin/kamctlrc is taken as base config?

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.