Summary: | crontab group access should be better documented | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Gil Kloepfer <gbz> |
Component: | New packages | Assignee: | No maintainer - Look at https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers if you want to take care of it <maintainer-needed> |
Status: | CONFIRMED --- | ||
Severity: | enhancement | CC: | cron-bugs+disabled, mgorny |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Gil Kloepfer
2009-03-17 05:55:52 UTC
(In reply to comment #0) > 750/root/cron, and sys-process/vixie-cron puts a directory called crontab under I mistakenly reference the directory in several places in this bug as /var/spool/cron/crontab instead of /var/spool/cron/crontabs (with an s at the end). The bug is valid, but my spelling of the directory wasn't!! Sorry about that. To quote http://www.gentoo.org/doc/en/cron-guide.xml : "No matter which cron package you use, if you want to allow a user to use crontab, he will first have to be in the cron group." I.e. adding the user to cron.allow (or removing him from cron.deny) is not enough. Thanks for the tip. This solved my problem, and I was able to undo my workaround. I'd suggest, then, that this be added to the man page for the crontab command rather than just having it on the cron guide in the online manual. For those of us who have used the *NIX cron system for years, we're typically not going to go to a guide telling us how to use cron. On other Linux distros (RHEL for one) needing to be in a specific group to use the crontab command is not a requirement. To emphasize, I think that the requirement to be in the cron group to use crontab is a good idea (it is consistent with similar Gentoo access controls), but I also feel it would be helpful for this to be documented in the crontab manual page on Gentoo as well. there is no central crontab man page (every cron implementation installs their own copy). if a cron implementation is installing with setgid cron perms on the binaries, then we should probably change that so it's consistent with the others. |