On my Debian system, /var/log/syslog contains an entry for each cron job which is executed …
Jan 17 20:10:01 machine1 /USR/SBIN/CRON[1545]: (convict) CMD (fetchmail -s >/dev/null 2>&1)
Jan 17 20:17:01 machine1 /USR/SBIN/CRON[1800]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Jan 17 20:20:01 machine1 /USR/SBIN/CRON[1914]: (convict) CMD (fetchmail -s >/dev/null 2>&1)
If your job is being executed by cron, you should find a reference to it in /var/log/syslog.
For the benefit of future readers searching for smmsp
on Server Fault:
smmsp
The smmsp
(SendMail Message Submission Program) user and group are specific to the Sendmail package and are not used by Postfix – or any other Mail Transfer Agent (MTA).
smmsp
is the default user that Sendmail uses if you haven’t configured a specific non-root user for the sendmail command to run as. It was introduced as a security measure so that vulnerabilities in sendmail couldn’t provide an exploiter with root access to the system.
From the Sendmail Installation and Operation Guide
The binary for sendmail is located in /usr/sbin
. It should be set-group-ID smmsp
See also Add smmsp to /etc/passwd from Sendmail, 4th Edition (O’Reilly).
Checking for / Removing Sendmail
From the information provided in the question, both Postfix and Sendmail are installed (and running) simultaneously. This can be verified by running,
dpkg -l | grep sendmail
To avoid conflict between the two MTAs, remove the Sendmail package(s) listed by the previous command.
It seems that many other users who thought that they’d removed Sendmail had, in fact, only uninstalled the sendmail-base
and sendmail
packages so they had to remove the following packages:
aptitude purge sendmail-bin sendmail-cf sendmail-doc
Here's a related post from another user who thought that they had uninstalled Sendmail from their system: Postfix/Sendmail: Frequent emails from smmsp to root.
Best Answer
These syntaxes are valid for all working days a 8:00 AM :
0 8 * * 1-5 /path/to/command >/dev/null 2>&1
0 8 * * 1,2,3,4,5 /path/to/command >/dev/null 2>&1
as you said @aleksandar-pavićMore explanations with these links :
The use of
>/dev/null 2>&1
is optional, the goal is to redirect all the outputs to /dev/null.You must have another problem, you must also specify the user if you use crontab -e
Here is a reminder of the cron syntax