Date: Thu, 7 Nov 2013 19:39:47 -0800 From: Lyndon Nerenberg <lyndon@orthanc.ca> To: Allan Jude <freebsd@allanjude.com> Cc: freebsd-current@freebsd.org Subject: Re: cron(8) improvement Message-ID: <D5199AC5-61E9-4D58-B31E-51E47F1CCFDF@orthanc.ca> In-Reply-To: <527BCA55.2000207@allanjude.com> References: <52792B60.1030309@allanjude.com> <488180AE-5C23-402A-BAA4-E3263D8C52BF@kientzle.com> <1383788977.14448.44112617.6F0D61A0@webmail.messagingengine.com> <527AFAA1.1040001@allanjude.com> <CA%2B7WWSdFFk4npy0=TOWO=6RApv5-wuJASHhE87eUf52DjQrxjw@mail.gmail.com> <D260751E-85D2-4591-88E0-5EFE1821D532@orthanc.ca> <CA%2B7WWSf_%2BBg8rjLdN1j032G2P81odfmQe-Ejyq7A4CqyqPqiAA@mail.gmail.com> <527BCA55.2000207@allanjude.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Nov 7, 2013, at 9:13, Allan Jude <freebsd@allanjude.com> wrote:
> Right. The best way to handle this is likely to have the ports install
> the example cron to ${PREFIX}/share/portname/ or wherever else they
> normally put examples, with instructions in the pkg-message on how to
> enable the cron. The same way that ports that add something to apache
> don't install to the apache etc/apache22/Includes/ directory, but
> instead tell you to add the lines to a file there.
It’s probably better to have the port’s rc.d script verify the crontab is in place, and install it if it’s not.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?D5199AC5-61E9-4D58-B31E-51E47F1CCFDF>