As I recall, if admin leaves a blank /etc/cron.deny and no /etc/cron.allow then all users will have access to cron.
That isn't working for me in one isolated case (a gentoo install inside a windows vm). What else can cause this behavior? I've looked at permissions on /var/spool/cron, subdir, and files. They match my other installations where users can access cron. I use the tried and true vixie-cron. -- [email protected] mailing list
