Alan McKinnon <[email protected]> writes:
> The answer is spelled out in detail, covering all possible combinations, in
> the man page (assuming you are talking about vixie-cron which afaik is the
> only one LPI covers).
>
> In other words, there is no excuse for not knowing exactly how it works.
Well, I'm certainly confused :)
The statement that I've seen a couple of times that "if neither file exists
then only suport user can use crontab" doesn't fit with my quick experiment
on Ubuntu 8.04 and my reading of the Lenny crontab(1) man page.
Yeah, I finally found reference to these files on Ubuntu. I didn't expect
them in the crontab(1) (ie. user) man page.
The Ubuntu and Debian crontab(1) page states:
If the /etc/cron.allow file exists, then you must be listed therein in
order to be allowed to use this command. If the /etc/cron.allow file
does not exist but the /etc/cron.deny file does exist, then you must not
be listed in the /etc/cron.deny file in order to use this command. If
neither of these files exists, then depending on site-dependent
configuration parameters, only the super user will be allowed to use this
command, or all users will be able to use this command. For standard
Debian systems, all users may use this command.
Nice waffling on the super user vs all user access. But it does default to
the "no /etc/cron.* files means access for all" rule.
Regards,
--
g. matthew rice <[email protected]> starnix care, toronto, ontario, ca
phone: 647.722.5301 x242 gpg id: EF9AAD20
http://www.starnix.com professional linux services & products
_______________________________________________
lpi-examdev mailing list
[email protected]
http://list.lpi.org/cgi-bin/mailman/listinfo/lpi-examdev
