Feeling a bit foolish for not being able to troubleshoot this, but here goes:

I've created a cronjob on Fedora 23 using command - ~$crontab -e

Crontab -l reports - ~$20 20 * * * user /home/user/bash-script
At 20 minutes of hour 20, user executes the following bash script /home/user/bash-script > /tmp/user-cron.log.

The cronjob doesn't run.
Crontab log in /var/log is empty.
User-cron.log in /tmp is empty.

"bash-script" is definitely executable.
No super-spy stuff in it -- it's simply making a tarball of directory:

#/bin/bash
cd /home/user && setfacl -R -b /home/user/stuff && tar -cJvf stuff-$(date +%Y-%m-%d-%H-%M-%S).tar.xz /home/user/stuff

I've stopped and restarted the crond daemon --

systemctl stop crond.service
systemctl start crond.service

Cron daemon is currently running --

9953 ? 00:00:00 crond

When I run bash-script manually from terminal it does exactly what it's supposed to do without errors.

I can't see what I'm missing to get the cronjob to work.

Thanks for your help.

~$ is part of the cronjob, or ??? (that should not be)
in crontab do the following:
and check the log

1 members found this post helpful.

please show us the output of crontab -l.
which setfacl are you trying to use ?
try modifying the script to look like this:

no - ~$
it was only meant to imitate the terminal prompt.

[user@userland]$ crontab -l
SHELL=/bin/bash
PATH=/sbin:/bin:/usr/sbin:/usr/bin
MAILTO=root

# For details see man 4 crontabs

# Example of job definition:
# .---------------- minute (0 - 59)
# | .------------- hour (0 - 23)
# | | .---------- day of month (1 - 31)
# | | | .------- month (1 - 12) OR jan,feb,mar,apr ...
# | | | | .---- day of week (0 - 6) (Sunday=0 or 7) OR sun,mon,tue,wed,thu,fri,sat
# | | | | |
# * * * * * user-name command to be executed

20 20 * * * user /home/user/bash-script > /tmp/user-cron.log

NAME
setfacl - set file access control lists

SYNOPSIS
setfacl [-bkndRLPvh] [{-m|-x} acl_spec] [{-M|-X} acl_file] file ...

setfacl --restore=file

DESCRIPTION
This utility sets Access Control Lists (ACLs) of files and directories. On the command line, a sequence of commands is followed by a sequence of files (which in turn can be fol‐
lowed by another sequence of commands, ...).

also which date are you trying to use ?

modified the bash script as you suggested and reset the time for the cronjob.
should know whether it works in approx 3 - 4 mins.

thanks for your help and suggestions.

/usr/bin/date


\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\

crud --- the changes in previous post did not work.
cronjob did not execute at 29 minutes past 18th hour as reset in crontab.

i tried this and ended up with an empty file:i changed it to this and file has hello world in it:

1 members found this post helpful.

G-E-N-I-U-S ! !
Cronjob started moments ago.
The crontab entry functions WITHOUT indicating the "user" executing the command.

Nice deduction.
Thank you, Schneidz.

As per https://serverfault.com/questions/35...-specific-user