PRs for manpage 'pw(8)'
This is an experimental report containing PRs for manpage 'pw(8)' as of Fri Apr 18 07:38:51 2014 UTC. See notes.
PRs for manpage 'pw(8)':
|o||2014/03/17||bin/187653||pw(8): 'pw user mod' is creating users instead of changing them.|
|o||2014/01/11||bin/185666||pw(8): Regression for 'pw usermod <user> -G <grouplist>' [regression]|
|o||2013/10/29||bin/183429||pw(8) returns "pw: user 'foo' disappeared during update" after freebsd-update upgrade|
|o||2012/11/28||bin/173977||mjg||pw(8) does not do range-checking on UIDs/GUIs from user's input, passwd DB becomes inconsistent|
|o||2012/10/22||bin/172965||pw(8): pw useradd does not allow -g ""|
|p||2012/06/26||bin/169471||[patch] pw(8) deletes group "username" on userdel even if group "username" is not assoc. w/user "username"|
|o||2012/06/23||bin/169356||pw(8): "pw groupmod GROUP -h FD" ignores "passwd_format" from login.conf(5)|
|o||2012/03/06||bin/165780||pw(8) should have a hook for home directory creation|
|o||2010/11/09||bin/152084||[patch] pw(8) does not allow @ or ! in gecos|
|o||2010/08/25||bin/149972||[patch] pw(8): usermod -u <non-numeric> should error|
|o||2009/01/26||bin/131013||pw(8) does not update NIS group file|
|o||2008/01/15||bin/119695||pw(8) does not interact with nscd(8)|
|o||2005/12/08||bin/90114||[patch] pw(8) takes strings after option -g for GID 0|
|s||2005/10/16||bin/87529||[request] pw(8): "pw lock", "pw unlock" should support the "-Y" option|
|o||2002/08/20||bin/41817||[patch] pw(8): pw groupshow doesn't include the login group|
|o||2002/05/02||bin/37672||pw(8) prints warnings after successful NIS map updates|
|o||2001/11/12||bin/31933||pw(8) can interpret numeric name as userid during userdel|
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.