Date: Tue, 01 Sep 2015 08:33:58 -0400 From: Ernie Luzar <luzar722@gmail.com> To: =?UTF-8?B?0KDRg9GB0LvQsNC9INCR0YPRgNGF0LDQvdC+0LI=?= <r100500b@gmail.com> Cc: freebsd-questions <freebsd-questions@freebsd.org> Subject: Re: how to change daily cron emails to go to user account instead of root Message-ID: <55E59B36.1050606@gmail.com> In-Reply-To: <CAGzH003c6dQUt48mTC3cXtqVXZF-334qwgU_obzF=StaPDkNEw@mail.gmail.com> References: <55DF057F.6040205@gmail.com> <55DF0C75.5000907@qeng-ho.org> <55DF0DB3.3040400@qeng-ho.org> <CAGzH002f-YFRMKweeBMvcLvkx1oxnsNMHTNPRJ%2B8rSCz4kxHBg@mail.gmail.com> <55E2F727.2040804@gmail.com> <55E2FDFA.7090301@qeng-ho.org> <CAGzH003c6dQUt48mTC3cXtqVXZF-334qwgU_obzF=StaPDkNEw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Руслан Бурханов wrote: > Ernie, look: > > Open you rc.conf, copy string and modify flags for cron daemon: > > cron_flags="-j 60 -m 'YOU@MAIL'" > > Then, restart cron daemon (it is not necessary reboot system): > > /etc/rc.d/cron restart > > Then take a look on cron process: > > ps auxww | grep cron > > If you doing all okey, it will be something like: > > root 561 0.0 0.1 7984 1528 ?? Is 3:16PM 0:00.01 > /usr/sbin/cron -j 60 -m YOU@MAIL -s > Thank you Руслан Бурханов for the informative reply. I did as you said and still the cron email went to root.instead of to bob. I edited rc.conf and added this cron_flags="-m 'bob@mydomain'" followed by "service cron restart" console command. ps auxww console command showed root 1953 0,0 0.2 10184 1940 - Is 1:05PM 0:00.30 /usr/sbin/cron -m bob@mydomain -s I am running version 10.2 on the host. In the /var/log/maillog file I can see postfix messages showing root receiving the emails. rc.conf hostname= option value is the same as the mydomain value in the cron_flags= option. Looks and acts like cron is not processing the over ride destination at daily cron security check time. Other than this problem of over ridding the cron email destination every thing seems to be working as one would expect. Is this enough to declare this a bug and submit a bug report? Can you suggest other tests I can do to help debug this problem? Thanks Ernie
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?55E59B36.1050606>