Summary: | vixie-cron doesn't work for non-root users due to permission problems | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Jim Faulkner <dogshu> |
Component: | [OLD] Core system | Assignee: | Cron Team <cron-bugs+disabled> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Jim Faulkner
2005-03-28 15:31:03 UTC
crontab gets installed setuid root so you should be able to edit crontabs. My mistake... /usr/bin/crontab was setuid to the wrong group... probably because I used a non-standard install method. I compiled the base system on a different machine, so the GID of the cron group probably differed on that machine. I fixed the ownership on /usr/bin/crontab, and editing crontabs now works fine for non-root users with the default /var/spool/cron/crontabs/ permissions. Sorry about the false alarm. I'm pretty sure this is INVALID, but one think you said made me curious enough to investigate. Was the system you originally compiled on a Gentoo system? cron group comes in the default /etc/group so it should be the same on all Gentoo systems (gid 16). Also, vixie-cron version? No, the machine I compiled it on was a Suse 9.1 system... GID 16 is the "dialout" group on the Suse system, which was the group that /usr/bin/crontab was chowned to before I fixed it. Next time I need to remember to use the --numeric-owner tar option when I compile Gentoo on a non-Gentoo system. I'm running vixie-cron-4.1-r4. Ah ok. That's what needed clarifying. Thanks. |