[prev in list] [next in list] [prev in thread] [next in thread] 

List:       freebsd-hackers
Subject:    Re: Improve cron(8)
From:       Willem Jan Withagen <wjw () digiware ! nl>
Date:       2014-06-25 8:20:01
Message-ID: 53AA8631.307 () digiware ! nl
[Download RAW message or body]

On 2014-06-23 18:53, Adrian Chadd wrote:
> On 23 June 2014 06:26, Tomek Wałaszek <tmwalaszek@gmail.com> wrote:
>
>> Hello,
>> I got your point.
>>  From the technical perspective it should be quite easy to implement this
>> feature, but I'm not sure whether this will get positive feedback. I
>> remeber that there was a discussion on the OpenBSD mailing lists (there was
>> even a patch for this) but they don't like the idea :) maybe FreeBSD
>> project will like it, I don't know.
>>
>> At the moment I want to update FreeBSD cron to ISC cron (with all the
>> features that FreeBSD has at the moment and ISC does not have) and
>> integrate atrun into cron like it was done in OpenBSD cron. After that (or
>> faster who knows :)) maybe we should have a discussion about this idea.
>
> Sweet!
>
> Well, hm. How should we do it? Can we run both cron's in the same
> source tree and just pick which to build/install? They're both
> different crons, right? Or is there a common ancestor that makes the
> diff not so terrible?

The /etc/rc.d/cron already allows for command_path specification.
So als long as the 2 versions have different nameing, selection is easy.

-_WjW


_______________________________________________
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org"
[prev in list] [next in list] [prev in thread] [next in thread]