Bug 53532
| Summary: | RFE: 'Basic' /etc/passwd causes 'pwck' errors | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Raw Hide | Reporter: | R P Herrold <herrold> |
| Component: | setup | Assignee: | Bill Nottingham <notting> |
| Status: | CLOSED RAWHIDE | QA Contact: | David Lawrence <dkl> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 1.0 | CC: | rvokal |
| Target Milestone: | --- | Keywords: | FutureFeature |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Enhancement | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2002-01-24 06:30: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: | |||
news, adm, and gopher are all legacy. gdm is fixed. |
Description of Problem: pwck is designed to 'preen' errors out of /etc/passwd, /etc/shadow, /etc/groups. and /etc/gshadow, nefore running pwconv and so forth. There is an explicit admonitionto run pwch before using pwconv, to avoid various erroes. Version-Release number of selected component (if applicable): error is through setup-2.4.7-1 How Reproducible: [root@cronos iso]# rpm -q shadow-utils ; pwck shadow-utils-20000826-4 user adm: directory /var/adm does not exist user news: directory /var/spool/news does not exist user uucp: directory /var/spool/uucp does not exist user gopher: directory /usr/lib/gopher-data does not exist user gdm: directory /home/gdm does not exist pwck: no changes [root@cronos iso]# Steps to Reproduce: As above Actual Results: As above Expected Results: Silent output (if a *nix command runs without error, it is by expectiation, silent) Additional Information: [Solution discussion] This implies that the SETUP package has to 'own' the 'home directories,' of the userid's which it considers important enough to install ... If a given userid is important enough to pre-seed into 'setup', this is proper -- Alternatiely, the userid list at: /usr/share/doc/setup-{shatever}/uidgid might be moved to /etc or to /etc/sysconfig [a better approach], and thus be formally available for consultation when a SPEC file calls for a adduser or useradd ... This would also enhance consistency ...