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

Site Navigation

PRs for tag 'rc.subr'

This is an experimental report containing PRs for tag 'rc.subr' as of 4-19-2014. GNATS has no finer-grained categorization than 'kern', 'bin', 'ports', and so forth. To augment this, the bugmeisters have adopted the convention of adding '[<tagname>]' to the Synopsis field. Consider this a prototype of a better search function.

This report is generated statically.

Please give feedback on this report to linimon@FreeBSD.org. Thanks.


PRs for tag 'rc.subr':
SSubmittedTrackerResp.Description
o2014/01/02conf/185429rc[rc.subr] ${name}_chroot does not work when there's a custom rc "start_cmd"
o2013/02/15conf/176181rc[rc.subr] rc.subr emitting warnings for non-defined xxx_enable vars, and errors/warnings not going to terminal
o2013/01/06conf/175079rc[rc.subr] [patch] rc.subr poorly handles recursive run_rc_command invocations
o2012/06/14conf/169047rc[rc.subr] [patch] /etc/rc.subr not checking some scripts (e.g. ruby running 'thin')
o2011/12/21conf/163508rc[rc.subr] [patch] Add "enable" and "disable" commands to rc.subr
5 problems total.

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.