Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 10 Nov 2013 17:59:23 +0100
From:      Philipp Ost <pj@smo.de>
To:        Warren Block <wblock@wonkity.com>, Daniel O'Connor <doconnor@gsoft.com.au>
Cc:        FreeBSD Current <freebsd-current@freebsd.org>, Matthew Seaman <matthew@freebsd.org>
Subject:   Re: cron(8) improvement
Message-ID:  <527FBB6B.5020706@smo.de>
In-Reply-To: <alpine.BSF.2.00.1311100912070.90718@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>

next in thread | previous in thread | raw e-mail | index | archive | help
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?

Philipp



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?527FBB6B.5020706>