From owner-freebsd-hackers@FreeBSD.ORG Mon Jun 23 20:05:58 2014 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8ED457DA; Mon, 23 Jun 2014 20:05:58 +0000 (UTC) Received: from mail-ob0-x231.google.com (mail-ob0-x231.google.com [IPv6:2607:f8b0:4003:c01::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3B1582EC6; Mon, 23 Jun 2014 20:05:58 +0000 (UTC) Received: by mail-ob0-f177.google.com with SMTP id uy5so4385812obc.8 for ; Mon, 23 Jun 2014 13:05:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=92R649d+Xn+sZDrfblxViOcq4YESQxplNT1LAGlLklc=; b=twfbUJxF+oiCLm78huUzgEUJeVohxjuma4vAFGTTqDzokBxN+lrox3iP5c2E4d9Ncf CTgtezGiSCuIauGbeJO32CjOWnaRNHk2uGMEJxMBbfgb7iwf9WKu64WLuw1RyqaAHqYG gkTiRmgwaXL0Djwm4hcI4D3WY413O0+Nz9/wvBlYgb34YHpLtvB6ES94QYAaz13cOzXC xWcOPXJOtY7IN6LsfmyOMBpm6Qz+vS67jqb4x/MqgNatLv7RJKdy0Ag+Dchvn0ZPf9nB 6WK5u5klmVcZg7Yld2VDBX3Nm2HteGkFBt++uM2TDi6ajq6A1mrAUlIADG7/hqYYvmfA rpkw== MIME-Version: 1.0 X-Received: by 10.60.176.163 with SMTP id cj3mr5647995oec.34.1403553957513; Mon, 23 Jun 2014 13:05:57 -0700 (PDT) Received: by 10.76.154.8 with HTTP; Mon, 23 Jun 2014 13:05:57 -0700 (PDT) In-Reply-To: <20140623194815.GQ93733@kib.kiev.ua> References: <53A72666.8090101@cox.net> <53A78C13.8030909@freebsd.org> <53A82008.9050002@digiware.nl> <20140623194815.GQ93733@kib.kiev.ua> Date: Mon, 23 Jun 2014 22:05:57 +0200 Message-ID: Subject: Re: Improve cron(8) From: =?UTF-8?Q?Tomek_Wa=C5=82aszek?= To: Konstantin Belousov Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18 Cc: "freebsd-hackers@freebsd.org" , Adrian Chadd , Willem Jan Withagen , Alfred Perlstein X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jun 2014 20:05:58 -0000 2014-06-23 21:48 GMT+02:00 Konstantin Belousov : > On Mon, Jun 23, 2014 at 09:33:38PM +0200, Tomek Wa??aszek wrote: > > 2014-06-23 18:53 GMT+02:00 Adrian Chadd : > > > > > On 23 June 2014 06:26, Tomek Wa??aszek 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 FreeBS= D > > > > project will like it, I don't know. > > > > > > > > At the moment I want to update FreeBSD cron to ISC cron (with all t= he > > > > 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? > > > > > > > > > -a > > > > > > > Hi, > > I don't quite follow you, who said that there will be cron's? There wil= l > be > > one cron, from the functional perspective it will work just like it is > > working now. The main differences will be that for example crontab will > not > > have suid, atrun will be integrated and it will for example has the > ability > > to run jobs from files in /var/cron.d but this will be not mandatory > > feature to use, /etc/crontab will stay. > > Could you, please, explain the methodology you use to ensure that > all local FreeBSD modifications to out version of the Vixie' cron > are carried forward together with the update ? > > We do not used the vendor imports/contrib workflow for the cron, > so FreeBSD-specific modifications are just sit there. The history > on head/usr.sbin/cron is huge, there is a lot of private changes > for the old codebase. > Hi, Yes, sure. The methodology is simple, if we can call this methodology. I download the new ISC CRON 4.1 and I'm going through the commit logs from usr.sbin/cron and adding the changes that were done in FreeBSD to ISC CRON 4.1. I don't know whether this is the best approach but I don't know any better at the moment. And this is still work in progress, not all of the changes are there. At first I was thinking of leaving ISC CRON 4.1 alone and only take care of the parts that were done in OpenBSD like atrun integration and poking cron via unix-domain socket. But on the FreeBSD ideas page there is written that the cron implementation is outdated and should be update to ISC cron. So I started doing it. --=20 Best regards, Tomasz Wa=C5=82aszek