root@sys-jira:~# crontab -l
# Edit this file to introduce tasks to be run by cron.
#
# Each task to run has to be defined through a single line
# indicating with different fields when the task will be run
# and what command to run for the task
#
# To define the time you can provide concrete values for
# minute (m), hour (h), day of month (dom), month (mon),
# and day of week (dow) or use '*' in these fields (for 'any').#
# Notice that tasks will be started based on the cron's system
# daemon's notion of time and timezones.
#
# Output of the crontab jobs (including errors) is sent through
# email to the user the crontab file belongs to (unless redirected).
#
# For example, you can run a backup of all your user accounts
# at 5 a.m every week with:
# 0 5 * * 1 tar -zcf /var/backups/home.tgz /home/
#
# For more information see the manual pages of crontab(5) and cron(8)
#
# m h dom mon dow command
35 11 * * * rsync -av --progress --log-file=/mnt/NFS/$(date +%Y%m%d)_rsync.log /opt /mnt/NFS/sys-jira
30 11 * * * rsync -av --progress --log-file=/mnt/NFS/$(date +%Y%m%d)_rsync1.log /var/lib/mysql /mnt/NFS/sys-jira
45 23 * * * rsync -av --progress --log-file=/mnt/NFS/$(date +%Y%m%d)_rsync2.log /var/atlassian /mnt/NFS/sys-jira
В /var/log/syslog пишет что нибудь в установленное время? Попробуйте указать полный путь к rsync. Возможно PATH не содержит /usr/bin, крон запускает команды не в баше, а в /bin/sh, что обычно является симлинком на /bin/dash.
The entire command portion of the
line, up to a newline or % character, will be executed by /bin/sh or by the shell specified in the SHELL variable
of the crontab file. Percent-signs (%) in the command, unless escaped with backslash (\), will be changed into
newline characters, and all data after the first % will be sent to the command as standard input. There is no way
to split a single command line onto multiple lines, like the shell's trailing "\".
3. grep -i cron *
crontab:# Edit this file to introduce tasks to be run by cron.
crontab:# Notice that tasks will be started based on the cron's system
crontab:# Output of the crontab jobs (including errors) is sent through
crontab:# email to the user the crontab file belongs to (unless redirected).
crontab:# For more information see the manual pages of crontab(5) and cron(8)
group:crontab:x:102:
group-:crontab:x:102:
gshadow:crontab:!::
gshadow-:crontab:!::
login.defs:# It should remove any at/cron/print jobs etc. owned by
mime.types:text/x-crontab
rsyslog.conf:#cron.* /var/log/cron.log
rsyslog.conf: cron,daemon.none;\