Date: Tue, 20 May 2003 21:28:00 -0700 From: Murray Stokely <murray@FreeBSD.org> To: Tom Rhodes <trhodes@FreeBSD.org> Cc: freebsd-doc@FreeBSD.org Subject: Re: cvs commit: www/en/docproj handbook3.sgml Message-ID: <20030520212800.U8403@freebsdmall.com> In-Reply-To: <200305210121.h4L1LfLI066670@repoman.freebsd.org>; from trhodes@FreeBSD.org on Tue, May 20, 2003 at 06:21:41PM -0700 References: <200305210121.h4L1LfLI066670@repoman.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, May 20, 2003 at 06:21:41PM -0700, Tom Rhodes wrote: > Log: > The cron(8) documentation task is complete. Ok, I think this section would be clearer if you maybe start with a simpler example than the system crontab file. There is a lot of junk in there (/etc/crontab) and I think it is confusing. Maybe if you just examine one line at a time. Maybe list one line, then talk about it (with a callout list to point to each field), then list another line, showing off a different aspect of cron's functionality, and then talk about that example line. See the ppp chapter for an example of a callout list describing the fields in a text file (/etc/ttys). I just don't think we need to list the whole crontab file. (and of course, someone will submit a PR the moment that /etc/crontab gets updated reminding us to update this chapter!) Also, I think you should just tell new users to edit their own crontab file with 'crontab -e'. This invokes the editor and I think is easier than telling them to create a file then install that file. crontab -e is one less step and makes it easier for new users. Thanks for writing this. We've needed a crontab section for a long time! - Murray
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030520212800.U8403>