My crontab looks like:
root@slack13x64:~# crontab -l -u dnd
# some variables
SHELL=/bin/bash
PATH=/bin:/usr/bin:/usr/local/bin:/home/dnd/bin
MAILTO=root
# Actual jobs
40 20 * * * /home/dnd/cron_jobs/some_job.sh
55 23 * * Fri /home/dnd/cron_jobs/other_job.py
Jobs run nearly OK, because crontab fails to set all variables:
Sep 1 20:40:01 slack13x64 crond[2325]: failed parsing crontab for user dnd: SHELL=/bin/bash
Sep 1 20:40:01 slack13x64 crond[2325]: failed parsing crontab for user dnd: PATH=/bin:/usr/bin:/usr/local/bin:/home/dnd/bin
Sep 1 20:40:01 slack13x64 crond[2325]: failed parsing crontab for user dnd: MAILTO=root
OS: slackware 13 x64, crontab 4.4
The question is what am I missing? Was support for setting initial env vars removed from crontab or user which runs this job should be assigned to some group?