Bug 234504 - cron(8) manual content error
Summary: cron(8) manual content error
Status: New
Alias: None
Product: Base System
Classification: Unclassified
Component: conf (show other bugs)
Version: 12.0-RELEASE
Hardware: Any Any
: --- Affects Many People
Assignee: freebsd-bugs mailing list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-12-30 16:33 UTC by Joe Barbish
Modified: 2018-12-30 22:47 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Joe Barbish 2018-12-30 16:33:27 UTC
The last sentence of the second paragraph under the Description heading of cron(8)says.

"The cron utility also searches for /etc/crontab and files in /etc/cron.d and /usr/local/etc/cron.d which are in a different format (see crontab(5))."

On review of crontab(5) there is no mention of a "different" format for those 2 paths, IE: /etc/cron.d and /usr/local/etc/cron.d

I think the second paragraph needs to be rewritten to clarify to the reader exactly what the cron utility is expecting as a control file.

The following is my draft of what it should say.


The cron utility uses a file formatted as defined by crontab(5) to control it's actions. The host system default is /etc/crontab which should not be changed. Additional crontab(5) defined files with unique file names may be placed in /etc/cron.d or /usr/local/etc/cron.d also /var/cron/tabs may contain files named after accounts in the /etc/passwd file as documented in crontab(1). File content read from these path locations are merged together and loaded into memory for use by the cron utility.
Comment 1 Joe Barbish 2018-12-30 22:47:01 UTC
After reading what I posted I see I was not very clear about what needed to be changed. 

Only the second paragraph under the Description heading of cron(8) needs to be replaced with the following paragraph content.

The cron utility uses a file formatted as defined by crontab(5) to control it's actions. The host system default is /etc/crontab which should not be changed. Additional crontab(5) defined files with unique file names may be manually placed in the /etc/cron.d or /usr/local/etc/cron.d directories. Also the /var/cron/tabs directory may contain crontab(5) defined files named after accounts in the /etc/passwd file as documented in crontab(1). File content read from these directory locations are merged together and loaded into memory for use by the cron utility. Issuing the "service cron restart" command from the root host console will refresh the cron utility's in memory controls.