Date: Mon, 23 Jun 2014 21:51:31 +0200 From: Willem Jan Withagen <wjw@digiware.nl> To: Alfred Perlstein <alfred@freebsd.org> Cc: Eitan Adler <lists@eitanadler.com>, "freebsd-hackers@freebsd.org" <freebsd-hackers@freebsd.org> Subject: Re: Improve cron(8) Message-ID: <7A2B44CF-DF48-46C7-9ACE-313E7DF5412B@digiware.nl> In-Reply-To: <53A87A9B.8060201@freebsd.org> References: <CAN3T69vCQTb1hU%2BAUKg%2BKLgsuCttLxYS6u2r9k3w5LM2D4zZoA@mail.gmail.com> <53A72666.8090101@cox.net> <53A78C13.8030909@freebsd.org> <53A82008.9050002@digiware.nl> <CAF6rxgk8_z8CFNyC6MDSdpnX1VAxwJ5xbFL3zY4kVw283ozfbA@mail.gmail.com> <53A87A9B.8060201@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Op 23 jun. 2014 om 21:06 heeft Alfred Perlstein <alfred@freebsd.org> het vol=
gende geschreven:
>=20
> On 6/23/14, 11:28 AM, Eitan Adler wrote:
>> On 23 June 2014 05:39, Willem Jan Withagen <wjw@digiware.nl> wrote:
>>> On 2014-06-23 4:08, Alfred Perlstein wrote:
>>>> On 6/22/14 11:54 AM, John D. Hendrickson and Sara Darnell wrote:
>>>>> Eitan Adler wrote:
>>>>>> +arch since hackers@ seems to be silent.
>>>>>>=20
>>>>>> On 11 June 2014 23:56, Tomek Wa=C5=82aszek <tmwalaszek@gmail.com> wro=
te:
>>>>>>> Hello,
>>>>>>> I saw on the FreeBSD Ideas page topic about cron :).
>>>>>>> I've started updating the 'original' FreeBSD cron from sources to
>>>>>>> vixi cron
>>>>>>> 4.1. I think (well I hope :P) most of the features that were done in=
>>>>>>> FreeBSD cron are now ported into vixi cron 4.1, there are unfortunat=
ely
>>>>>>> some missing features at the moment:
>>>>>>> - @every_second - this need to be done
>>>>>>> - -s and -o, in vixi cron 4.1 daylight time switches are enabled by
>>>>>>> default, at the moment there is no -s and -o options. So you need to=
>>>>>>> remove
>>>>>>> '-s' from the cron rc script
>>>>>>>=20
>>>>>>> I've also added one feature from OpenBSD, crontab is poking cron usi=
ng
>>>>>>> unix-domain socket so we don't need to have suid on crontab.
>>>>>>>=20
>>>>>>> Path is in the attachment. I'm testing it on my FreeBSD box and it
>>>>>>> looks
>>>>>>> good but anyway don't try it on production machines :).
>>>>>>>=20
>>>>>>> After the installation we have to do a few things:
>>>>>>> - Add crontab group
>>>>>>> - Change group to crontab on /var/cron/tabs
>>>>>>> - Add sticky bit on /var/cron/tabs
>>>>>>> - Add group write permissions on /var/cron/tabs
>>>>>>>=20
>>>>>>> This is still work in progress but if someone could have a look on
>>>>>>> this and
>>>>>>> give me some feedback it would be great.
>>>>>>>=20
>>>>>>> Regards,
>>>>>>> Tomasz Walaszek
>>>=20
>>>=20
>>>>> you should up the version number or start your own renamed application=
>>>=20
>>>> Tomek, please don't let messages like this dissuade you from
>>>> participating. Please do continue this work, it seems very promising.
>>>> Thank you!
>>>>=20
>>>> I was myself looking forward to having these additions. Very cool.
>>>=20
>>> Hi Tomek,
>>>=20
>>> One of the things I like in some of the other cron's is the possibility t=
o
>>> add files to something like: /var/cron.d.
>>> This as contract to /var/cron/tabs, where files need to <username> and a=
re
>>> executed under that users privilidges.
>>>=20
>>> Reason that this would be convenient is that tools like puppet don't nee=
d to
>>> start editing files to remove crontab lines. Which IMHO is always more h=
airy
>>> then just adding/deleting/updating a file called:
>>> /var/cron.d/tool-ABC.cron
>> This is absolutely useful and has existed in every large scale
>> envrionment I know of.
> Agreed, it would be a huge step forward for FreeBSD.
>=20
IT is more or less how most tools operate now a days.
- global config file
Aka /etc/crontab
- local config file=20
Aka /etc/crontab.local
- directory (1 or more)
Aka /var/cron/tabs with users
And /var/cron.d for separate files with cron content.
--WjW=20=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7A2B44CF-DF48-46C7-9ACE-313E7DF5412B>