Date: Mon, 11 Nov 2013 10:28:00 +0100 From: Stefan Esser <se@freebsd.org> To: freebsd-current@freebsd.org Subject: Re: cron(8) improvement Message-ID: <5280A320.9020705@freebsd.org> In-Reply-To: <alpine.BSF.2.00.1311101023080.91068@wonkity.com> References: <52792B60.1030309@allanjude.com> <488180AE-5C23-402A-BAA4-E3263D8C52BF@kientzle.com> <1383788977.14448.44112617.6F0D61A0@webmail.messagingengine.com> <527AFAA1.1040001@allanjude.com> <CA%2B7WWSdFFk4npy0=TOWO=6RApv5-wuJASHhE87eUf52DjQrxjw@mail.gmail.com> <D260751E-85D2-4591-88E0-5EFE1821D532@orthanc.ca> <CA%2B7WWSf_%2BBg8rjLdN1j032G2P81odfmQe-Ejyq7A4CqyqPqiAA@mail.gmail.com> <527BCA55.2000207@allanjude.com> <D5199AC5-61E9-4D58-B31E-51E47F1CCFDF@orthanc.ca> <527C5D52.7030508@allanjude.com> <047405A8-B6EB-427B-A2E4-6254DD1A077B@orthanc.ca> <CA%2B7WWSfiWT4wprOS8oQS5YaeE%2BjjyxfK5fzAyFz8XMyX_J%2BoLw@mail.gmail.com> <3E6377FF-69FE-48E4-BFB1-E5095A7FA1BB@orthanc.ca> <527C6DEF.6020102@allanjude.com> <527E3EB3.6000301@FreeBSD.org> <8034B822-F903-43D1-8BF6-DFAD7C22F5B0@gsoft.com.au> <alpine.BSF.2.00.1311100912070.90718@wonkity.com> <527FBB6B.5020706@smo.de> <alpine.BSF.2.00.1311101023080.91068@wonkity.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Am 10.11.2013 18:23, schrieb Warren Block: > On Sun, 10 Nov 2013, Philipp Ost wrote: >> Warren Block schrieb: >> [...] >> 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. I like the idea that entries are ignored unless they end in ".cron". This does not only allow to install inactive cron scheduled in a file ending in ".cron.sample", it also lets you rename modified cron tabs to e.g. ".cron.off" (a convention often used by me). If the port is re-installed, it is up the administrator to decide whether a schedule based on a freshly installed ".cron.sample" or the old ".cron.off" should be enabled. This would require the deinstall target / tool to rename any cron entry of the port / package by appending ".off", but that's a minor change, IMHO. This might lead to some clutter in ".../cron.d/", but I do not think that stale files should be automatically removed (even if they were older than some threshold). Regards, STefan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5280A320.9020705>