I don't want to see the result of command

[guif]

I use the typical commands to install a progrma (./configure, make, make install,...) into an script.
Is it possible to don't see the output of this commands?

[nmset]

script &> /dev/null

But that's a bad idea !

[coopstah13]

if you don't see the output, how will you know things were successful or not?

[Rubberman]

script &> /dev/null

But that's a bad idea !

Indeed! Better to pipe the output to a file. Then you can see if there were any problems. IE: script &> /tmp/script.out

[nmset]

If that's what guif wants, which was not very clear from his request, he'd better do the following :

script | tee somelogfile

This way, you can follow the output on screen at the same time it is being logged.

[Rubberman]

That's what I love about 'nixes - there are so many ways to "skin the cat"! It is the ultimate renunciation of the Windoze "one size fits all" philosophy.

[guif]

so good! /dev/null is the solution.
thanks!

[Dustspeck]

That's not quite what people are saying...

It is recommended that you save the output for 'just in case'.

The reason for saving the output is that if there is some issue, you might be able to review the log and find the issue. If you throw the output away without looking at it, there might have been a problem and you'd never know what it was and what caused it.

When installing widget, I'd use:
( ./configure && make && make install ) 2>&1 | tee ~/widget.`date +%Y%m%d%H%M%S`.log

That way you'd see the output and it would get saved for later. As well, repeated attempts to install the software wouldn't over-write the previous log files.

If you wanted to avoid having the output display, you could still use:
( ./configure && make && make install ) 2>&1 > ~/widget.`date +%Y%m%d%H%M%S`.log

You could run the individual commands with an announcement in the file with:
logfile="widget.`date +%Y%m%d%H%M%S`.log"
( echo ; echo "----------" ; echo "Configuring widget" ; echo "----------" ; ./configure ) 2>&1 >> $logfile

or
( echo -e "\n----------\nConfiguring widget\n----------" ; ./configure ) 2>&1 >> $logfile

*note the quotes are the reverse single quote. It runs the command and puts the output in place.

[guif]

thank you Dustspeck.
/dev/null is an example.
I put this:

./configure && make && make all >> /tmp/all_output.log 2>&1

[Dustspeck]

The parentheses group the output and are important in keeping the output together.

./configure && make && make all >> /tmp/all_output.log 2>&1

is not equivalent to

( ./configure && make && make all ) >> /tmp/all_output.log 2>&1

In the first example, only the output from the make all command is stored in the log file.