PRs for tag 'rc.subr'
This is an experimental report containing PRs for tag 'rc.subr' as of 5-30-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':
| S | Submitted | Tracker | Resp. | Description |
|---|---|---|---|---|
| o | 2014/01/02 | conf/185429 | rc | [rc.subr] ${name}_chroot does not work when there's a custom rc "start_cmd" |
| o | 2013/02/15 | conf/176181 | rc | [rc.subr] rc.subr emitting warnings for non-defined xxx_enable vars, and errors/warnings not going to terminal |
| o | 2013/01/06 | conf/175079 | rc | [rc.subr] [patch] rc.subr poorly handles recursive run_rc_command invocations |
| o | 2012/06/14 | conf/169047 | rc | [rc.subr] [patch] /etc/rc.subr not checking some scripts (e.g. ruby running 'thin') |
| o | 2011/12/21 | conf/163508 | rc | [rc.subr] [patch] Add "enable" and "disable" commands to rc.subr |
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.