Date: Tue, 01 Sep 2015 15:31:22 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 202814] cron_flags="-m mailto not used by periodic routines Message-ID: <bug-202814-8@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202814 Bug ID: 202814 Summary: cron_flags="-m mailto not used by periodic routines Product: Base System Version: 10.2-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Many People Priority: --- Component: conf Assignee: freebsd-bugs@FreeBSD.org Reporter: joeb1@a1poweruser.com Trying to change daily cron emails to go to user account instead of root. I edited rc.conf and added this cron_flags="-m bob@mydomain" followed by "service cron restart" console command. Then issuing "ps auxww | grep cron" console command showed root 1953 0,0 0.2 10184 1940 - Is 1:05PM 0:00.30 /usr/sbin/cron -m bob@mydomain -s But that night the periodic emails still went to root. On the questions list Arthur Chance <freebsd@qeng-ho.org> explained that periodic routines reroutes its output independent of cron's settings. Adding this to periodic.conf is the work-a-round daily_output="user@dom.ain" weekly_output="$daily_output" monthly_output="$daily_output" daily_security_output="$daily_output" weekly_security_output="$daily_output" monthly_security_output="$daily_output" where "user@dom.ain" would be "bob@mydomain" This work-a-round should not be required if the logic of periodic adhered to the man cron specs. All the cron periodic routines need to be modified to be aware of the cron_flags="-m 'bob@mydomain'" option and use it's value as the destination email address. Would also be nice if error messages were issued for invalid values. Should also work for any host user name like cron_flags="-m bob", IE no mydomain needed for any user on same host. -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-202814-8>