summaryrefslogtreecommitdiff
path: root/docs-xml/Samba-EventLog-HOWTO.txt
diff options
context:
space:
mode:
authorBjörn Jacke <bj@sernet.de>2009-05-26 15:40:21 +0200
committerBjörn Jacke <bj@sernet.de>2009-05-26 16:23:11 +0200
commitcaeae66c5bb3a4a600b5c90be97d98a323d1dc2f (patch)
treefdff8e7b6a21b09ddb03865eb948cea3e5eafeb0 /docs-xml/Samba-EventLog-HOWTO.txt
parent6b7bd3757005286c528d3bb0c6790e0d8651eaaf (diff)
downloadsamba-caeae66c5bb3a4a600b5c90be97d98a323d1dc2f.tar.gz
samba-caeae66c5bb3a4a600b5c90be97d98a323d1dc2f.tar.bz2
samba-caeae66c5bb3a4a600b5c90be97d98a323d1dc2f.zip
s3:pam_smbpass: don't call openlog() or closelog() from pam_smbpass
Patch from Steve Langasek with tiny fixes by me to make it apply to master. Also see Debian bug #434372 and bugzilla #4831. Calling openlog() or closelog() inside a pam module is not good as these functions are not stackable and no program won't re-do openlog() just because a pam module might have called closelog().
Diffstat (limited to 'docs-xml/Samba-EventLog-HOWTO.txt')
0 files changed, 0 insertions, 0 deletions