PRs for manpage 'cron(8)'
This is an experimental report containing PRs for manpage 'cron(8)' as of Fri May 30 07:36:36 2014 UTC. See notes.
PRs for manpage 'cron(8)':
| S | Submitted | Tracker | Resp. | Description |
|---|---|---|---|---|
| o | 2013/01/02 | bin/174905 | [patch] make cron(8) honor rfc821, rfc5321, rfc2076, rfc3834 | |
| o | 2009/11/05 | bin/140304 | [patch] add MAILFROM ability to cron(8) | |
| o | 2009/02/18 | bin/131853 | cron(8): please add support for CRON_TZ and CRON_WITHIN | |
| o | 2008/01/10 | bin/119524 | cron(8) suddenly stops working, not crash | |
| o | 2006/10/25 | bin/104809 | cron(8): incorrect cron behavior with mday field = "*/N" | |
| o | 2006/05/08 | bin/97002 | [patch] cron(8) fails quietly if /usr/sbin/sendmail is missing | |
| o | 2001/01/20 | bin/24485 | [patch] to make cron(8) handle clock jumps |
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.