16 авг. 2021 г. · It means that stderr ( 2 - containing error messages from the executed command or script) is redirected ( >& ) to stdout ( 1 - the output of the command)

27 авг. 2010 г. · The first version redirects stdout to /dev/null, and the second redirects both stdout and stderr to /dev/null.

5 нояб. 2021 г. · The commands are performing two redirects: > /dev/null redirects Standard Output to /dev/null; 2>&1 redirects Standard Error to Standard ...

11 авг. 2014 г. · I am running the following command every 5 minutes in my crontab to keep Phusion Passenger alive. */5 * * * * wget mysite.com > /dev/null 2>&1

24 сент. 2014 г. · Another way of doing the second redirect would be 2>&1 which means "send output to fd 2 to fd 1" (and as fd 1 is going to /dev/null this output ...

16 авг. 2012 г. · You have piped the second commands STDOUT and STDERR to /dev/null, and only piped the first command's STDOUT to the second command.

1 нояб. 2013 г. · The first command sends stdout to /dev/null then 2>&1 causes stderr (standard error) to be sent to where stdout(standard output) is going which ...

1 мар. 2011 г. · I've tried redirecting STDOUT and STDERR using "&>" and also "2>&1" and neither seems to work. I still get e-mailed by this cron job (every ...

11 сент. 2019 г. · I am seeing a random behavior when copying from one server to another using rsync to the /dev/null of the destination server.

17 мая 2021 г. · I think i figured it out, my solution is: Revert the exec command: exec 1>&2 2>&-. Do the command. Restore the old exec: exec 2>&1.