Skip site navigation (1)Skip section navigation (2)

Site Navigation

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)':
o2014/03/17bin/187653pw(8): 'pw user mod' is creating users instead of changing them.
o2014/01/11bin/185666pw(8): Regression for 'pw usermod <user> -G <grouplist>' [regression]
o2013/10/29bin/183429pw(8) returns "pw: user 'foo' disappeared during update" after freebsd-update upgrade
o2012/11/28bin/173977mjgpw(8) does not do range-checking on UIDs/GUIs from user's input, passwd DB becomes inconsistent
o2012/10/22bin/172965pw(8): pw useradd does not allow -g ""
p2012/06/26bin/169471[patch] pw(8) deletes group "username" on userdel even if group "username" is not assoc. w/user "username"
o2012/06/23bin/169356pw(8): "pw groupmod GROUP -h FD" ignores "passwd_format" from login.conf(5)
o2012/03/06bin/165780pw(8) should have a hook for home directory creation
o2010/11/09bin/152084[patch] pw(8) does not allow @ or ! in gecos
o2010/08/25bin/149972[patch] pw(8): usermod -u <non-numeric> should error
o2009/01/26bin/131013pw(8) does not update NIS group file
o2008/01/15bin/119695pw(8) does not interact with nscd(8)
o2005/12/08bin/90114[patch] pw(8) takes strings after option -g for GID 0
s2005/10/16bin/87529[request] pw(8): "pw lock", "pw unlock" should support the "-Y" option
o2002/08/20bin/41817[patch] pw(8): pw groupshow doesn't include the login group
o2002/05/02bin/37672pw(8) prints warnings after successful NIS map updates
o2001/11/12bin/31933pw(8) can interpret numeric name as userid during userdel
17 problems total.


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 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.