Sam Varshavchik wrote:
Some buggy versions of cron or at run commands without providing a
standard error and/or standard output and/or standard input.
like i said stock redhat, this is at-3.1.8-23. so, if lots of people
haven't observed and reported this bug then something must be unique
about my system. am i the only one? if anyone would like to comment on
success/failure in reproducing this i'd appreciate it. i just reproduced
it with a newer version of courier.
it all works great for nonpriv users. why does it not work for root?
does anyone else use batch to run root commands?
Try putting the following nonsense before the command:
exec >/dev/null; exec 2>/dev/null; exec 1</dev/null;
lol, i guess. i'm aware that one workaround is to handle the output in
the job as opposed to allowing at to pass it to courier. sinking the
output in /dev/null does prevent at from piping to courier, but it
doesn't get it delivered in email.
a workaround:
# batch <<eof
echo '(echo this is a test; date) |mail -s "batch output" root'
eof
please help:
- anyone else observe this?
- why fd's screwed for only root user?
16 messages in net.sourceforge.lists.courier-usersRe: [courier-users] Re: no mail from ...
