Date: Wed, 06 Nov 2013 21:27:45 -0500 From: Allan Jude <freebsd@allanjude.com> To: freebsd-current@freebsd.org Subject: Re: cron(8) improvement Message-ID: <527AFAA1.1040001@allanjude.com> In-Reply-To: <1383788977.14448.44112617.6F0D61A0@webmail.messagingengine.com> References: <52792B60.1030309@allanjude.com> <488180AE-5C23-402A-BAA4-E3263D8C52BF@kientzle.com> <1383788977.14448.44112617.6F0D61A0@webmail.messagingengine.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --mnl3j66O5oaxIWoeiLcLWuFTRJwMQAcqw Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 2013-11-06 20:49, Mark Felder wrote: > > On Wed, Nov 6, 2013, at 18:21, Tim Kientzle wrote: >> On Nov 5, 2013, at 9:31 AM, Allan Jude <freebsd@allanjude.com> wrote: >> >>> This came up in discussion on IRC and I thought I should throw it at = the >>> list so I don't forget. >>> >>> A user was asking how to do what linux cron does, where there is a >>> directory /etc/cron.d/ that packages and add files to to create cront= abs. >>> >>> Making FreeBSD's cron (Vixie Cron) include /etc/cron.d/ and >>> /usr/local/etc/cron.d/ in the /etc/crontab format seems like a very >>> useful feature, especially for pkg(8) as it makes it easy and safe to= >>> programatically add and remove crontabs as part of a package. >> This is a good idea. We should do it. >> >> How and if this facility gets used is a separate question. >> >> "Tools, not policy." >> >> Support for a cron.d directory is a tool that can be >> used in many ways. The policy of how it should be >> used is a separate discussion. (For example, whether >> or not ports or packages should install crontab files into >> /usr/local/etc/cron.d/ can be richly debated after that >> directory exists.) >> > Ok, so we create that directory. Now nobody can use it in a port until > FreeBSD 8.4 is EoL -- approximately June 30, 2015. > > We should be using the existing cron tabs directory *now*. We can't > easily force older versions of FreeBSD to update their cron software or= > configuration to support that new directory. > > I'm not saying we shouldn't create it, just that we can't effectively > use it for 2 years. > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.o= rg" My use case is less about packages, and more about puppet, ansible etc. Puppet relies on these hideously large markers in the crontab files to programmatically add/remove crons, whereas a cron.d directory could be done nice and clean And in that case, the fact that it is not supported on 8.x does not bother me. --=20 Allan Jude --mnl3j66O5oaxIWoeiLcLWuFTRJwMQAcqw Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (MingW32) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJSevqjAAoJEJrBFpNRJZKft/UQAMGIBi7ojv9QXLk94gKY0G8y uBdknSngAZOapxbdwRAPky8diRoGs0a5PRJ/VQblXo6B7gG+EfzfwjM2XwVh9hOs mzJ2EEFG7s5g763fNWcF6yf+CNWN5aoDqcZDLDYfDhfyadZsJ4R0AruPVyJoGLxC WcbWmCz94d8A+AQv9sD9MT89dhM8tyTi2wGNQFsnCnRYGTJ4XkDwKzKZWyv7oS5v 4A7ijVYHGpSPtYAyXz5jrWuDn668UqbC1oEg33bcUu87JDb/m4Cnytfa2VTkAkpr oIhXthduEfa/p97trSItfWuDAPEiAdc6I9iGOrrN+fBT+rqCmFHPmnALDT/aGFvr 7F3tlqsGuibsF5LCJOIm0CMzl/MrkacPRTdnz7y7qqz09pl+mKWM29H+TvikkxQ4 I6RxgdVGoy3FggGJKw8Q98IKg4jJaw+aqguGyPnfbV1RfiPU7AIzgmlG53NzeUfN NnzPZdq3V0aFPNhbr4N/zXPmBZhze4zt6AFADncUBziqrKv66CWicPzX7B339OGP k4axBSxgbLpKnPE9bF7/8o9yUo6M9EF3sLJgEsevlZk9ktcMhfk6/b4MvQtI05LX Dkj2NdBuWTzUePh9iOu+RgaoSbFArNTCSdqXyl9Yel+CZOJB28JZQ3o6j+8Rpz7i b4dgeFeuf1lezG/w2Awz =OdyH -----END PGP SIGNATURE----- --mnl3j66O5oaxIWoeiLcLWuFTRJwMQAcqw--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?527AFAA1.1040001>