open("/etc/cron.allow", O_RDONLY) = -1 ENOENT (No such file or
open("/etc/cron.deny", O_RDONLY) = -1 ENOENT (No such file or
You (thomasz) are not allowed to use this program (crontab)
See crontab(1) for more information
If the cron.allow file exists, then you must be listed therein
to be allowed to use this command. If the cron.allow file
exist but the cron.deny file does exist, then you must not be
the cron.deny file in order to use this command. If neither
files exists, only the super user will be allowed to use this
This is not a bug - as the manpage which you quoted states:
If neither of these files exists, only the super user will
be allowed to use this command.
That means that if neither /etc/cron.allow nor /etc/cron.deny exist,
only the superuser (root) can use crontab.
This is new and breaks things, vixie-cron should include and install
an empty /etc/cron.deny when updating.
should be fixed as of mailman-2.1.5-10
we no longer use crontab, but rather install a mailman cron script in
/etc/cron.d, which is not supposed to have the same restriction. This
has some other advantages as well.
sorry, I edited the wrong bugzilla apparently :-(