Hi!
On Sun, 2014-09-07 at 20:13:37 +0200, Joachim Breitner wrote:
> the latest version of haskell-dbus is failing on the BSDs, as it started
> to use getPeerCred in haskell-network. That is only available if the
> following configure.ac snippet detects it:
[…]
> Would you care to see if this is
Hi,
the latest version of haskell-dbus is failing on the BSDs, as it started
to use getPeerCred in haskell-network. That is only available if the
following configure.ac snippet detects it:
dnl --
dnl * test for SO_PEERCRED and struct ucred
dnl -
Please, could you test (on io.debian.org and asdfasdf.debian.net) whether
adding above mentioned defines directly in getpeercred.c really works?
I have added the above defined in the top my getpeercred.c and have
written a simple test and it seems to work.
I added defines into our svn in ,
it
On Fri, 2008-06-06 at 22:10 +0200, Petr Salinger wrote:
> It looks like a problem in our headers. On plain FreeBSD contains
>
> /* Socket options. */
> #define LOCAL_PEERCRED 0x001 /* retrieve peer credentials */
> #define LOCAL_CREDS 0x002 /* pass credentials to receiver
I'm the maintainer of nss-ldapd. There is a slight problem on
kfreebsd-i386 and kfreebsd-amd64.
What is the best way on these architectures to get information about
clients that connect through a named socket?
It looks like a problem in our headers. On plain FreeBSD contains
/* Socket options
Hello list (I'm not subscribed so please keep me in Cc).
I'm the maintainer of nss-ldapd. There is a slight problem on
kfreebsd-i386 and kfreebsd-amd64.
What is the best way on these architectures to get information about
clients that connect through a named socket?
I currently use this code:
ht
6 matches
Mail list logo
