PRs for manpage 'passwd(1)'
This is an experimental report containing PRs for manpage 'passwd(1)' as of Tue Mar 11 07:38:24 2014 UTC. See notes.
PRs for manpage 'passwd(1)':
|p||2012/09/19||bin/171779||[patch] passwd(1): make option NO_FSCHG incomplete|
|o||2008/12/10||bin/129541||[nis] passwd(1) cannot be forced to "yp" mode in some circumstances.|
|o||2008/02/29||bin/121243||des||[patch] passwd(1) patch for usage with PAM/LDAP|
|o||2007/11/04||bin/117812||passwd(1): incapable of changing LDAP passowrds using passwd in FreeBSD 7.0|
|o||2006/05/10||bin/97083||[patch] passwd(1) does not support _PWF_HESIOD|
|s||2004/09/02||bin/71290||des||[patch] passwd(1) cannot change passwords other than NIS/local (e.g. via pam_ldap)|
|s||2003/11/24||bin/59638||des||passwd(1) does not use PAM to change the password|
|o||2002/10/02||bin/43582||[patch] passwd(1) fails on nonexistent users|
GNATS has no finer-grained categorization than 'kern', 'bin', 'ports', and so forth. To augment this, the bugmeisters have adopted the convention of adding '<name>(<section>)' to the Synopsis field. Consider this a prototype of a better search function.
Please give feedback on this report to linimon@FreeBSD.org. Thanks.
Bugs can be in one of several states:
- o - open
- A problem report has been submitted, no sanity checking performed.
- a - analyzed
- The problem is understood and a solution is being sought.
- f - feedback
- Further work requires additional information from the originator or the community - possibly confirmation of the effectiveness of a proposed solution.
- p - patched
- A patch has been committed, but some issues (MFC and / or confirmation from originator) are still open.
- r - repocopy
- The resolution of the problem report is dependent on a repocopy operation within the CVS repository which is awaiting completion.
- s - suspended
- The problem is not being worked on, due to lack of information or resources. This is a prime candidate for somebody who is looking for a project to do. If the problem cannot be solved at all, it will be closed, rather than suspended.
- c - closed
- A problem report is closed when any changes have been integrated, documented, and tested -- or when fixing the problem is abandoned.