On 12/07/2014 06:48 PM, jdd wrote:
in /etc/crontab, I read:
# check scripts in cron.hourly, cron.daily, cron.weekly, and cron.monthly # -*/15 * * * * root test -x /usr/lib/cron/run-crons && /usr/lib/cron/run-crons >/dev/null 2>&1
I'm not good enough to understand what mean the end of the line:
/dev/null 2>&1
but my logs are full of
déc. 07 18:15:01 linux-uegt CRON[6561]: pam_unix(crond:session): session closed for user root
prg > /dev/null means to redirect the 1st file descriptor to /dev/null, and a subsequent 2> &1 means to redirect the 2nd file descriptor to the same as the first one. While the regular program output (stdout, standard output, file descriptor 1) and the error diagnostics (stderr, standard error, file descriptor 2) are redirected to the null device, i.e., it's discarded, other components being used may still use other output channels. In this cases, the PAM authentication module is jumping into game when cron opens a "session". I also saw these annoying logs, but didn't find a working idea how to avoid or suppress this. Hints found via google either tried to avoid to open a session for cron (/etc/pam.d/cron), or tried to discard the output in the logger (whatever syslog program you are using: I personally installed good'ol rsyslog. Have a nice day, Berny -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org