That's cause wget uses stderr for some of it's output. The second one should work.
–
theotherreceiveJul 17 '09 at 3:08

2

Incidentally, you might want to save that wget output to a log file, so when/if your download stops working, you can figure out why. If it's in a script anyway. If this is a one-off type run, then yea, to the trash
–
Matt SimmonsJul 17 '09 at 3:17

1

For wget you can use the -q options to make it quiet.
–
pkhamreMar 30 '12 at 10:12

Any way to suppress output written directly to /dev/tty?
–
d11wtqJul 17 '14 at 7:08

How low of a level would you like to know?
–
Matt SimmonsMay 29 '11 at 13:54

1

@nomoreink: it's actually 2 commands, one is > file and the second one is 2>&1. The first one redirects the standard out to a file. The second one takes 2nd file descriptor and redirects it to first one. You can do the reverse, redirect standard output to standard error using >&2 and then redirect standard error to a file with 2> file.
–
Hubert KarioNov 27 '12 at 11:39

If you need to hide the output without letting the program know it by checking the output/error file descriptor you can try using the following in a shell:

stty flusho; command ;stty -flusho

or if you just want to hide input from the terminal by the way:

stty -echo; command ;stty echo

See stty(1) manual page for more information

For Linux all i know is that Ubunutu (10.04 "Lucid") and some "Debian/Arch" (commented below - tnx hendry) doesn't have the flusho setting (and i can't see anything other appropriate in the man-page). The echo setting works on the Ubuntu anyway.