Bug 177132
Summary: | rhdb fails to start/stop when certain pam modules are enabled | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 3 | Reporter: | Eric Jon Rostetter <eric.rostetter> |
Component: | pam | Assignee: | Tomas Mraz <tmraz> |
Status: | CLOSED ERRATA | QA Contact: | Jay Turner <jturner> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3.0 | CC: | srevivo, tgl |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-05-04 11:40:07 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Eric Jon Rostetter
2006-01-06 16:02:22 UTC
BTW, I "fixed" this on my system by commenting out the redirection to /dev/null for the input on the su commands... Now works for me fine. Not sure why the redirect is there, but it certainly works for me without it. Why is pam invoked at all during "su" from root to another ID? I should think that that breaks a ton of stuff besides Postgres ... The reason for the redirect is exactly to make sure that the postmaster process isn't associated with any specific tty --- else it could be killed by typing control-C on the tty, which you probably don't want. (I'm not sure if that's true on RHEL3 in particular, but there definitely are Unixen where it would be true.) The RHEL distribution contains a /etc/pam.d/su file which by default acts this way. Why? Don't know; I'm not Red Hat nor the pam authors, etc. I understand associating it with a tty can cause various "problems" of sort. But I think the pam issue is potentially more serious. I'll leave Red Hat to decide which is more serious, or how to resolve the conflicts. One could question if this isn't really a bug in the pam modules, in that they should fail more gracefully if there is no tty available? I'm not qualified to rule on that issue though. Yeah, I think it's a pam issue as well. Reassigning ... PAM package with fixed pam_access was released in RHEL3U7 Beta. Errata containing fixed pam_access was released. |