Bug 112765
Summary: | yppasswd problem | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Ed Friedman <edfriedmangvs> |
Component: | ypserv | Assignee: | Steve Dickson <steved> |
Status: | CLOSED WONTFIX | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 1 | CC: | mattdm |
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-07-18 18:20:59 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
Ed Friedman
2003-12-30 22:51:50 UTC
The /usr/local/etc/passwd file seems to get changed, but the NIS database doesn't. If I cd to /var/yp and make passwd, then the database gets changed, but it doesn't get propogated. It seems I have to reboot (or kill the ypbind and ypserv daemons, then restart them) to propogate the change. As a regular user (instead of root), I get the message: Error while changing the NIS password. While killing and restarting the ypserv daemon seems to be sufficient to propagate changes made via yppasswd, if the passwd file or the group file are edited manually, then restarting the daemon does not propagate the changes. While manual changes to the passwd file can be propagated by doing any yppasswd change, then restarting the ypserv daemon, I have not yet discovered any way to propagate changes to the group file. This is stupid hack, but I run a cronjob once an hour to: make -C /var/yp to work arround this problem. Fedora Core 1 is maintained by the Fedora Legacy project for security updates only. If this problem is a security issue, please reopen and reassign to the Fedora Legacy product. If it is not a security issue and hasn't been resolved in the current FC5 updates or in the FC6 test release, reopen and change the version to match. Thanks! NOTE: Fedora Core 1 is reaching the final end of support even by the Legacy project. After Fedora Core 6 Test 2 is released (currently scheduled for July 26th), there will be no more security updates for FC1. Please use these next two weeks to upgrade any remaining FC1 systems to a current release. |