diff options
| author | Rich Megginson <rmeggins@redhat.com> | 2010-03-01 15:03:30 -0700 |
|---|---|---|
| committer | Rich Megginson <rmeggins@redhat.com> | 2010-03-01 18:45:50 -0700 |
| commit | 142900b2757378bfbff34e3f390fcb1a292eea91 (patch) | |
| tree | 77f675339d01cae94cdc7374a2cdb8af22b01de2 /ldap/admin/src/start.c | |
| parent | 9aec0f110d8238de66ebbf2f6eb71cb363220c40 (diff) | |
| download | ds-142900b2757378bfbff34e3f390fcb1a292eea91.tar.gz ds-142900b2757378bfbff34e3f390fcb1a292eea91.tar.xz ds-142900b2757378bfbff34e3f390fcb1a292eea91.zip | |
Bug 551198 - LDAPI: incorrect logging to access log389-ds-base-1.2.6.a2
https://bugzilla.redhat.com/show_bug.cgi?id=551198
Resolves: bug 551198
Bug Description: LDAPI: incorrect logging to access log
Reviewed by: nkinder (Thanks!)
Branch: HEAD
Fix Description: The connection logging code was not ldapi/unix socket
aware. Now we check for the socket type, and check to see if there is
a proper path name in the path field. The "server" side of the socket
seems not to get the path name set correctly - not sure why, but it doesn't
really matter, since the client side path name does seem to be set
correctly. The access log will contain the server side path and the client
side path, so something like "from local to /var/run/slapd-foo.socket"
Platforms tested: RHEL5 x86_64, Fedora 11 x86_64
Flag Day: no
Doc impact: no
Diffstat (limited to 'ldap/admin/src/start.c')
0 files changed, 0 insertions, 0 deletions