Bug 157107 - [PATCH] Not all debugging statements in pam_krb5 actually work with 'debug' option
[PATCH] Not all debugging statements in pam_krb5 actually work with 'debug' o...
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: pam_krb5 (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Nalin Dahyabhai
Brian Brock
: Patch
Depends On:
  Show dependency treegraph
Reported: 2005-05-06 17:35 EDT by wingc
Modified: 2012-06-20 12:57 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2012-06-20 12:57:14 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
make sure that all debug() statements are called when debugging is enabled (1.33 KB, patch)
2005-05-06 17:35 EDT, wingc
no flags Details | Diff

  None (edit)
Description wingc 2005-05-06 17:35:51 EDT
Description of problem:

Some of the debugging statements in src/minikafs.c are wrapped inside
conditionals like this:

    if (options->debug > 1) {

The only problem is that options->debug can only equal 0 or 1 when pam_krb5
parses its options. There is no way to get all the debugging output when you
specify 'debug' in the PAM configuration files.

Version-Release number of selected component (if applicable):

Tested on pam_krb5-2.1.2-1 from RHEL4

How reproducible:


Steps to Reproduce:
1. Add 'debug' to the command line options for pam_krb5, e.g. in
Actual results:

Not all the debugging statments from src/minikafs.c generate output in the syslog.

Expected results:

Some of the missing debugging output would have been useful, such as "got error
determining file server for cell", etc.

Additional info:

A patch to fix this problem is at:

Comment 1 wingc 2005-05-06 17:35:51 EDT
Created attachment 114101 [details]
make sure that all debug() statements are called when debugging is enabled
Comment 2 Jiri Pallich 2012-06-20 12:57:14 EDT
Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life. 
Please See https://access.redhat.com/support/policy/updates/errata/

If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue.

Note You need to log in before you can comment on or make changes to this bug.