Bugzilla Bug 67531

Because /etc/cron.hourly/logsentry.cron is not set +x by the ebuild, it's not
sufficent to uncomment the logwatch-line in this file to run logsentry hourly
via this script. It has to be set +x to be executed, because
/usr/sbin/run-crons checks if the script is executable instead of sourcing it.

chmod u+x /etc/cron.hourly/logsentry.cron does the trick

(or add the line directly to root's crontab, as the ebuild says).

Reproducible: Didn't try
Steps to Reproduce:
1. emerge logsentry
2. ls -l /etc/cron.hourly


Actual Results:  
~: ls -l /etc/cron.hourly
-rw-r--r--  1 root root 168 Oct 12 20:31 logsentry.cron

Expected Results:  
~: ls -l /etc/cron.hourly
-rwxr--r--  1 root root 168 Oct 12 20:31 logsentry.cron

Fixed.  Thanks for the report.