a) Is it not a bit worrisome that logwatch automatically attempts to add itself to the root crontab? I'm not sure how I feel about any package touching the root/system crontab without intervention or option. b) Having said that, logwatch fails at the above task when using fcron. Output is as follows: grep: /var/spool/cron/crontabs/root: No such file or directory * adding to cron... /usr/sbin/ebuild.sh: line 58: /var/spool/cron/crontabs/root: No such file or directory The ebuild Reproducible: Always Steps to Reproduce: 1. use fcron as your cron 2. emerge logwatch 3. watch logwatch fail at cron addition Actual Results: Logwatch fails to add itself as a cron job Expected Results: As intended by the ebuild, logwatch should have successfully added itself to cron. I cannot agree that logwatch should in any way add itself to the root/system crontab without any form of user intervention or action. At the most, a simple message describing how to add it yourself should be put in pkg_postinst(), or multi-cron capable code be placed in pkg_config(). Again, I do not want any package touching something like the system crontab without warning or my authority.
marty, wanna handle this? I agree it should not add itself to the crontab
changed to message
