| commit | caeae66c5bb3a4a600b5c90be97d98a323d1dc2f | |
| author | Björn Jacke <bj@sernet.de> | |
| Tue, 26 May 2009 13:40:21 +0000 (26 15:40 +0200) | ||
| committer | Björn Jacke <bj@sernet.de> | |
| Tue, 26 May 2009 14:23:11 +0000 (26 16:23 +0200) | ||
| tree | fdff8e7b6a21b09ddb03865eb948cea3e5eafeb0 | treesnapshot (tar.gz zip) |
| parent | 6b7bd3757005286c528d3bb0c6790e0d8651eaaf | commitdiff |
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().
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().