명령어 출력을 파일에 쓰는 기본적으로 일반적인 10가지 방법

Write the output of a command to a file, Basically 10 commonly used ways

출처: Byte Commander

Overview:

Please note that the n.e. in the syntax column means "not existing".
There is a way, but it's too complicated to fit into the column. You can find a helpful link in the List section about it.

List:

• command > output.txt
• The standard output stream will be redirected to the file only, it will not be visible in the terminal. If the file already exists, it gets overwritten.
• command >> output.txt
• The standard output stream will be redirected to the file only, it will not be visible in the terminal. If the file already exists, the new data will get appended to the end of the file.
• command 2> output.txt
• The standard error stream will be redirected to the file only, it will not be visible in the terminal. If the file already exists, it gets overwritten.
• command 2>> output.txt
• The standard error stream will be redirected to the file only, it will not be visible in the terminal. If the file already exists, the new data will get appended to the end of the file.
• command &> output.txt
• Both the standard output and standard error stream will be redirected to the file only, nothing will be visible in the terminal. If the file already exists, it gets overwritten.
• command &>> output.txt
• Both the standard output and standard error stream will be redirected to the file only, nothing will be visible in the terminal. If the file already exists, the new data will get appended to the end of the file..
• command | tee output.txt
• The standard output stream will be copied to the file, it will still be visible in the terminal. If the file already exists, it gets overwritten.
• command | tee -a output.txt
• The standard output stream will be copied to the file, it will still be visible in the terminal. If the file already exists, the new data will get appended to the end of the file.
• (*)
• Bash has no shorthand syntax that allows piping only StdErr to a second command, which would be needed here in combination with tee again to complete the table. If you really need something like that, please look at "How to pipe stderr, and not stdout?" on Stack Overflow for some ways how this can be done e.g. by swapping streams or using process substitution.
• command |& tee output.txt
• Both the standard output and standard error streams will be copied to the file while still being visible in the terminal. If the file already exists, it gets overwritten.
• command |& tee -a output.txt
• Both the standard output and standard error streams will be copied to the file while still being visible in the terminal. If the file already exists, the new data will get appended to the end of the file.