PRs for manpage 'login(1)'
This is an experimental report containing PRs for manpage 'login(1)' as of Fri May 30 07:37:50 2014 UTC. See notes.
PRs for manpage 'login(1)':
S | Submitted | Tracker | Resp. | Description |
---|---|---|---|---|
a | 2006/10/01 | bin/103873 | csjp | login(1) SEGFAULT on unsuccessful login |
o | 2006/03/03 | bin/94051 | login(1): IP network in login.access ignored unless DNS is down | |
o | 2005/02/08 | bin/77261 | login(1) doesn't chdir into a group-protected home directory | |
o | 2004/12/22 | bin/75378 | login(1): login/wtmp/utmp not updating properly | |
o | 2004/07/22 | bin/69398 | [patch] login(1) cleartext display of password in login.c | |
o | 2004/01/14 | bin/61355 | login(1) does not restore terminal ownership on exit | |
o | 2002/12/18 | bin/46352 | [patch] login(1) open file descriptors and signal handling in the child login process |
Notes
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.