LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (http://www.linuxquestions.org/questions/slackware-14/)
-   -   Cron [may be bug with perms] (http://www.linuxquestions.org/questions/slackware-14/cron-%5Bmay-be-bug-with-perms%5D-869721/)

anti_user 03-20-2011 01:59 AM

Cron [may be bug with perms]
 
Hello! I found strange in logs of crontab...
Its may be permission problem, but this machine working with default slackware installation...
Code:

Mar 16 22:01:32 darkstar crond[1736]: /usr/sbin/crond 4.4 dillon's cron daemon, started with loglevel notice
Mar 16 22:01:32 darkstar atd[1737]: Cannot change to /var/spool/atjobs: Permission denied
Mar 16 22:13:57 darkstar crond[1737]: /usr/sbin/crond 4.4 dillon's cron daemon, started with loglevel notice
Mar 16 22:13:57 darkstar atd[1738]: Cannot change to /var/spool/atjobs: Permission denied

Machine working on current 13.37

This bug resolved in http://bugs.gentoo.org/show_bug.cgi?id=111982 by change perms to 755 to /var/spool/atjobs

willysr 03-20-2011 03:07 AM

Strange, i don't find that error message on my log

Petri Kaukasoina 03-20-2011 04:01 AM

Quote:

Originally Posted by anti_user (Post 4296729)

This bug resolved in http://bugs.gentoo.org/show_bug.cgi?id=111982 by change perms to 755 to /var/spool/atjobs

Nope, in the gentoo problem the permissions were wrong for the ROOT directory /.

In slackware, /var/spool/atjobs should be mode 1770, user daemon, group daemon. Now when you changed it to 755, everyone can see who has atjobs, if you still can queue atjobs in the first place (you removed the write bit for group).

By the way, this has nothing to do with cron.


All times are GMT -5. The time now is 02:26 AM.