Bug 118985
Summary: | pam_console fails to give device ownership for diskless clients | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 3 | Reporter: | David J. Bianco <bianco> |
Component: | kernel | Assignee: | Peter Staubach <staubach> |
Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3.0 | CC: | petrides, tmraz |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-04-12 19:29:30 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
David J. Bianco
2004-03-23 16:39:59 UTC
Sorry for the immediate update. I forgot to add that the diskless client boots via tftp/PXE from an RHEL3 box, but the actual files are on a Netapp fileserver. I don't know if this makes a difference, because I think the problem is somewhere on the Linux side, but I figure I should add it for completeness. If the pam_console calls chown and it doesn't fail and the device isn't really chowned, how could this be a bug in pam? I'd bet on that it is some misconfiguration. David, thanks for the bug report. Could you please try to chown /dev/fd0 from root (to uid 4902) manually to see if this takes effect? If that doesn't work, I'll reassign this to someone who works on the associated file system (is it NFS?). If that does work, then it's not a kernel problem, so please give me some advice on which component should get this bug. Thanks. I tried this manually, and it worked fine: dlcc4:/home/bianco> lag /dev/fd0 brw-rw---- 1 root root 2, 0 Oct 11 13:28 /dev/fd0 dlcc4:/home/bianco> sudo chown 4902 /dev/fd0 dlcc4:/home/bianco> lag /dev/fd0 brw-rw---- 1 bianctst root 2, 0 Oct 11 13:28 /dev/fd0 dlcc4:/home/bianco> sudo chown root /dev/fd0 dlcc4:/home/bianco> lag /dev/fd0 brw-rw---- 1 root root 2, 0 Oct 11 13:28 /dev/fd0 I don't know if it's a kernel problem or not. Perhaps it's a PAM problem, or a glibc problem, or an NFS problem, or any of a number of other components that are involved in the process. Given that this problem is 18 months old, is there sufficient interest in this being investigated and possibly resolved? |