Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Can you explain the mechanism behind the following line in a script?
exec > >(tee logfile.txt)
this basically outputs both STDOUT to the console and also logfile.txt when it’s in a script. I know what it does, but I cannot explain exactly why it works the way it does. I understand >(command args) is a process substitution. My main confusion comes from why having extra “>”?
why not exec >(tee logfile.txt)?
See the help for
exec($ help exec). The relevant part isSince each command inherits its standard output from the shell that spawns it,
every command now has the given process substitution as its standard output, rather
than the terminal.