On Sun, 2007-02-04 at 20:50 -0600, [EMAIL PROTECTED] wrote:
> 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 caus
On 2/4/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
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.
I had to add users that needed acces
On Monday, 5 February 2007 13:20, [EMAIL PROTECTED] wrote:
> 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 thi
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, an
4 matches
Mail list logo
