From owner-freebsd-current@FreeBSD.ORG Sun Nov 10 17:23:33 2013 Return-Path: Delivered-To: freebsd-current@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 ESMTP id 52C16922; Sun, 10 Nov 2013 17:23:33 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id DCEE22648; Sun, 10 Nov 2013 17:23:32 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.7/8.14.7) with ESMTP id rAAHNVpi091226; Sun, 10 Nov 2013 10:23:31 -0700 (MST) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.7/8.14.7/Submit) with ESMTP id rAAHNUVA091222; Sun, 10 Nov 2013 10:23:30 -0700 (MST) (envelope-from wblock@wonkity.com) Date: Sun, 10 Nov 2013 10:23:30 -0700 (MST) From: Warren Block To: Philipp Ost Subject: Re: cron(8) improvement In-Reply-To: <527FBB6B.5020706@smo.de> Message-ID: References: <52792B60.1030309@allanjude.com> <488180AE-5C23-402A-BAA4-E3263D8C52BF@kientzle.com> <1383788977.14448.44112617.6F0D61A0@webmail.messagingengine.com> <527AFAA1.1040001@allanjude.com> <527BCA55.2000207@allanjude.com> <527C5D52.7030508@allanjude.com> <047405A8-B6EB-427B-A2E4-6254DD1A077B@orthanc.ca> <3E6377FF-69FE-48E4-BFB1-E5095A7FA1BB@orthanc.ca> <527C6DEF.6020102@allanjude.com> <527E3EB3.6000301@FreeBSD.org> <8034B822-F903-43D1-8BF6-DFAD7C22F5B0@gsoft.com.au> <527FBB6B.5020706@smo.de> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (wonkity.com [127.0.0.1]); Sun, 10 Nov 2013 10:23:31 -0700 (MST) Cc: FreeBSD Current , Matthew Seaman X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Nov 2013 17:23:33 -0000 On Sun, 10 Nov 2013, Philipp Ost wrote: > Warren Block schrieb: > [...] >>> ie either the file is named such that it is ignored by cron >>> (preferable IMO) or the entries in them are commented out. >> >> Why not just use an additional entry in rc.conf? >> >> rsnapshot_cron="YES" >> >> (If there is a /usr/local/etc/cron.d/rsnapshot, add it to cron on >> start/restart.) >> >> This brings up another problem. When a port is removed, what is done >> with ports cron entries that have been user modified? Normally, >> modified files would not be removed, but a cron entry for a removed port >> definitely should not be running any more, even if the admin forgot to >> remove the entry in rc.conf. But just removing the modified file is bad >> also, because maybe the port was just removed as part of an upgrade. > > Given the above scenario, would it be acceptable to set the entry in rc.conf, > $portname_cron=YES, to $portname_cron=NO without touching the modified files > and inform the user about having done so? I would not want the system modifying rc.conf for me, but don't have a better idea at present. Maybe move customized cronfiles to an "old" folder on deinstall, so at least the user could recover them.