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

Site Navigation

PRs for manpage 'su(1)'

This is an experimental report containing PRs for manpage 'su(1)' as of Fri May 30 07:39:33 2014 UTC. See notes.

PRs for manpage 'su(1)':
o2010/05/22ports/146816portmgr[patch] Mk/ loosen SU_CMD & su(1) cohesion for make {,rm}config
o2009/09/19bin/138961ldap groups don't work with su(1)
f2004/10/29bin/73261jillesSuspending su(1) sometimes hangs
f2003/06/19bin/53520jillessu(1) to another user does not update utmp
o2001/06/17bin/28223su(1) doesn't look at login.conf all the time
5 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.