[Chilli] [PATCH] adds option for chilli query TCP socket
david at coova.com
Mon Mar 5 08:33:28 UTC 2012
I applied and committed your patches. Thanks! However, I'll be making
some changes. For instance, it isn't good that chilli_query will default
to using the TCP port instead of the unix socket... I will change it to
only use the TCP socket if specified. Also, might as well allow for
chilli_query to use an IP other than localhost. It would be great if
you'd make these changes and submit another patch, otherwise I will do
On Thu, 2012-03-01 at 16:30 +0100, Peter Warasin wrote:
> Hi guys
> The attached patch adds the option "cmdsocketport" which allows to
> configure a TCP port instead of a UNIX socket path for the chilli_query
> If neither "cmdsocket" nor "cmdsocketport" is specified the default TCP
> port of 42424 will be opened.
> chilli_query accepts now an option -P which allows to specify the tcp
> port, if neither -P nor -s <unixsocketpath> is supplied tcp port 42424
> will be assumed.
> In many circumstances it is possible that somehow this unix socket file
> will be deleted by another process or by a second chilli process or by
> the sysadmin itself. You can imagine which issues that would cause when
> you rely on chilli query for a special service.
> Using tcp port this is not possible anymore.
> Hope this helps you guys too.
> The patch is against 1.2.6. If rebase is required, just tell me
> Chilli mailing list
> Chilli at coova.org
More information about the Chilli