Re: pid formatted incorrectly in debug message (wrong printf format?)

["Norman Gray" <gray [at] nxg.name>]

Arthur, hello.

On 8 Sep 2018, at 14:21, Arthur de Jong wrote:

> Yes, the pid should probably not be logged if it cannot be determined.
> I've just pushed a fix that should avoid logging unavailable
> information.

Thanks.

> I don't think that FreeBSD's LOCAL_PEERCRED facility exposes the
> process ID of the socket peer. I sadly can't test this at the moment
> because by FreeBSD virtual machine is not working. I'm not aware of 
> any
> other mechanism to find the PID of the nslcd client.

That's a pity.  I'd originally reported this on the FreeBSD bugzilla, 
and I've updated that report with this information: 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231234

Best wishes,

Norman


--
Norman Gray  :  https://nxg.me.uk
--
To unsubscribe send an email to
nss-pam-ldapd-users-unsubscribe@lists.arthurdejong.org or see
https://lists.arthurdejong.org/nss-pam-ldapd-users/