On Wednesday 01 April 2009 19:08:23 G. Matthew Rice wrote:
> <thomas.steud...@ckw.ch> writes:
> > What about /etc/cron.deny /etc/cron.allow?
> >
> > Sometimes it's not clear, what is valid right know.
> > What, if a user is in both files?
>
> These are implicitly mentioned in 213.4:
>
>
> https://group.lpi.org/publicwiki/bin/view/Examdev/LPIC-20x#213_4_Troublesho
>oting_environmen
>
> Namely, "cron configuration files". However, in looking through the man
> pages on my desktop, I can't find any mention of them in any of the man
> pages. That's not good. So, I'll add the allow/deny files in the next
> addendum, too.
man 1 crontab, second para in DESCRIPTION section:
If the cron.allow file exists, then you must be listed therein in
order to be
allowed to use this command. If the cron.allow file does not
exist but the
cron.deny file does exist, then you must not be listed in the
cron.deny file in
order to use this command. If neither of these files exists, only the
super user
will be allowed to use this command.
This vixie-cron-4.1 and cron.allow takes precedence over cron.deny if both
exist - the first sentence is always true without exception in the code.
> > Depends this on version/ distro of cron?
No, I have never seen a cron that does it any other way.
There are other minor crons that might do it differently, but that's niche
stuff.
> If the major distros are all using vixie cron, it should be consistent.
>
> Can anyone confirm RH again? :)
RH uses vixie-cron
--
alan dot mckinnon at gmail dot com
_______________________________________________
lpi-examdev mailing list
lpi-examdev@lpi.org
http://list.lpi.org/cgi-bin/mailman/listinfo/lpi-examdev
