On Wed, 2015-11-11 at 16:15 +0100, Axel Beckert wrote: > I didn't think about that. But doesn't cron (or actually run-parts) > then barf about a non-executable file?
Doesn't look like it: pabs@chianamo ~ $ mkdir foo pabs@chianamo ~ $ touch foo/bar pabs@chianamo ~ $ run-parts -- foo pabs@chianamo ~ $ (echo '#!/bin/sh' ; echo echo bar) > foo/bar pabs@chianamo ~ $ run-parts -- foo pabs@chianamo ~ $ chmod a+x foo/bar pabs@chianamo ~ $ run-parts -- foo bar > I'd prefer if I don't have to edit a script which likely changes with > every release. I'd rather prefer something like /etc/default/corekeeper > which is then sourced by that script if it exists. The package and the script is pretty much set in stone, it is unlikely any changes to either of them will be needed apart from bumping Standards-Version, at least once I have done the next upload. > BTW: What also would suffice would be to make the target e-mail > address configurable (preferably via /etc/default/corekeeper) so that > it doesn't go to root@`hostname`. I'm not sure how to send cron.daily output to a different address. -- bye, pabs https://wiki.debian.org/PaulWise
signature.asc
Description: This is a digitally signed message part
