On 06/27/2014 01:22 PM, Gelpi Andrea wrote:
Il 26/06/2014 19:09, Nigel Kukard ha scritto:
On 06/25/2014 02:57 PM, Gelpi Andrea wrote:
Hi,
     I'm trying to use socket instead of net communication.

  From http://wiki.policyd.org/cluebringer.conf I read

PROTO
Protocol to use "tcp" or "unix", defaults to "tcp"
HOST
IP to listen on, * for all. Blank for unix sockets. Defaults to *:
Port to run on, in the case of a unix socket it would be the path.
Defaults to 10031:

So I put in configuration:

proto=unix
host=
port=/var/lib/cluebringer/policyd.socket

In postfix main.cf I put
check_policy_service unix:/var/lib/cluebringer/policyd.socket

After restarting policyd I found in log:
2014/06/25-16:50:05 - 8984] [CORE] ERROR: 2014/06/25-16:50:05 Could not
determine port number from host [*]:/var/lib/cluebringer/policyd.socket

    at line 82 in file /usr/share/perl5/Net/Server/Proto.pm
[2014/06/25-16:50:05 - 8984] [CORE] NOTICE: 2014/06/25-16:50:05 Server
closing!


So I understand something is not correct in configuration.

Where I'm wrong?

While the config file may indicate unix as being supported, I believe
this is a copy and paste from a documentation page somewhere.

I don't think unix sockets are supported at this time (they may work),
but I recall a while back I looked into it and the changes required to
make it work were not that trivial.

Try commenting out  host=  and see if that works, failing that, try
comment it out in cbpolicyd.
I try to remove host from configuration file, with no success.
I try to comment it in cbploicyd and I get only error on host name.

Failing that, could you log an issue for this, it should definitely be
included in v2.1.

where have I to log in an issue?



https://gitlab.devlabs.linuxassist.net/policyd/policyd/issues

-N

_______________________________________________
Users mailing list
[email protected]
http://lists.policyd.org/mailman/listinfo/users_lists.policyd.org

Reply via email to