Change stdout/stderr output device

up vote
0
down vote

favorite

By default if we run

foo()
 echo "myfoo"

it will go to stdout. My question is, for a bash script or function, is there a programmatic way to change the device so that commands don't automatically write to stdout?

maybe something like this:

foo()
 mkfifo bar
 exec 1<>bar
 echo "myfoo" # this gets written to the bar named pipe?

so we "repoint" stdout somewhere else perhaps?

asked May 8 at 4:36

Alexander Mills

1,885929

yeah that doesn't seem to work. If i run tail -f bar I don't seem to get any data there.
â€“Â Alexander Mills
May 8 at 4:40

Are you asking for something very different from foo >bar?
â€“Â Kusalananda
May 8 at 4:58

@Kusalananda honestly, I might delete this question, this new question is better: unix.stackexchange.com/questions/442461/â€¦
â€“Â Alexander Mills
May 8 at 4:59

add a commentÂ |Â

up vote
0
down vote

favorite

By default if we run

foo()
 echo "myfoo"

it will go to stdout. My question is, for a bash script or function, is there a programmatic way to change the device so that commands don't automatically write to stdout?

maybe something like this:

foo()
 mkfifo bar
 exec 1<>bar
 echo "myfoo" # this gets written to the bar named pipe?

so we "repoint" stdout somewhere else perhaps?

asked May 8 at 4:36

Alexander Mills

1,885929

yeah that doesn't seem to work. If i run tail -f bar I don't seem to get any data there.
â€“Â Alexander Mills
May 8 at 4:40

Are you asking for something very different from foo >bar?
â€“Â Kusalananda
May 8 at 4:58

@Kusalananda honestly, I might delete this question, this new question is better: unix.stackexchange.com/questions/442461/â€¦
â€“Â Alexander Mills
May 8 at 4:59

add a commentÂ |Â

up vote
0
down vote

favorite

By default if we run

foo()
 echo "myfoo"

it will go to stdout. My question is, for a bash script or function, is there a programmatic way to change the device so that commands don't automatically write to stdout?

maybe something like this:

foo()
 mkfifo bar
 exec 1<>bar
 echo "myfoo" # this gets written to the bar named pipe?

so we "repoint" stdout somewhere else perhaps?

asked May 8 at 4:36

Alexander Mills

1,885929

By default if we run

foo()
 echo "myfoo"

it will go to stdout. My question is, for a bash script or function, is there a programmatic way to change the device so that commands don't automatically write to stdout?

maybe something like this:

foo()
 mkfifo bar
 exec 1<>bar
 echo "myfoo" # this gets written to the bar named pipe?

so we "repoint" stdout somewhere else perhaps?

asked May 8 at 4:36

Alexander Mills

1,885929

asked May 8 at 4:36

Alexander Mills

1,885929

asked May 8 at 4:36

Alexander Mills

1,885929

asked May 8 at 4:36

Alexander Mills

1,885929

yeah that doesn't seem to work. If i run tail -f bar I don't seem to get any data there.
â€“Â Alexander Mills
May 8 at 4:40

Are you asking for something very different from foo >bar?
â€“Â Kusalananda
May 8 at 4:58

@Kusalananda honestly, I might delete this question, this new question is better: unix.stackexchange.com/questions/442461/â€¦
â€“Â Alexander Mills
May 8 at 4:59

add a commentÂ |Â

yeah that doesn't seem to work. If i run tail -f bar I don't seem to get any data there.
â€“Â Alexander Mills
May 8 at 4:40

Are you asking for something very different from foo >bar?
â€“Â Kusalananda
May 8 at 4:58

@Kusalananda honestly, I might delete this question, this new question is better: unix.stackexchange.com/questions/442461/â€¦
â€“Â Alexander Mills
May 8 at 4:59

yeah that doesn't seem to work. If i run tail -f bar I don't seem to get any data there.
â€“Â Alexander Mills
May 8 at 4:40

Are you asking for something very different from foo >bar?
â€“Â Kusalananda
May 8 at 4:58

@Kusalananda honestly, I might delete this question, this new question is better: unix.stackexchange.com/questions/442461/â€¦
â€“Â Alexander Mills
May 8 at 4:59

add a commentÂ |Â

1 Answer
1

active

oldest

votes

up vote
0
down vote

This technique will probably do the trick:
Using process substitution, only send stderr to process

Basically, you call:

exec > $some_file

using process substitution, you can do something like:

exec > >( while read line; do echo " stdout: $line"; done )

that means that all stdout will go to that file instead of to the terminal.

answered May 8 at 4:50

Alexander Mills

1,885929

add a commentÂ |Â

Your Answer

StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
convertImagesToLinks: false,
noModals: false,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);

);

draft saved

draft discarded

StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f442460%2fchange-stdout-stderr-output-device%23new-answer', 'question_page');

);

Post as a guest

Name

1 Answer
1

active

oldest

votes

1 Answer
1

active

oldest

votes

up vote
0
down vote

This technique will probably do the trick:
Using process substitution, only send stderr to process

Basically, you call:

exec > $some_file

using process substitution, you can do something like:

exec > >( while read line; do echo " stdout: $line"; done )

that means that all stdout will go to that file instead of to the terminal.

answered May 8 at 4:50

Alexander Mills

1,885929

add a commentÂ |Â

up vote
0
down vote

This technique will probably do the trick:
Using process substitution, only send stderr to process

Basically, you call:

exec > $some_file

using process substitution, you can do something like:

exec > >( while read line; do echo " stdout: $line"; done )

that means that all stdout will go to that file instead of to the terminal.

answered May 8 at 4:50

Alexander Mills

1,885929

add a commentÂ |Â

up vote
0
down vote

This technique will probably do the trick:
Using process substitution, only send stderr to process

Basically, you call:

exec > $some_file

using process substitution, you can do something like:

exec > >( while read line; do echo " stdout: $line"; done )

that means that all stdout will go to that file instead of to the terminal.

answered May 8 at 4:50

Alexander Mills

1,885929

This technique will probably do the trick:
Using process substitution, only send stderr to process

Basically, you call:

exec > $some_file

using process substitution, you can do something like:

exec > >( while read line; do echo " stdout: $line"; done )

that means that all stdout will go to that file instead of to the terminal.

answered May 8 at 4:50

Alexander Mills

1,885929

answered May 8 at 4:50

Alexander Mills

1,885929

answered May 8 at 4:50

Alexander Mills

1,885929

answered May 8 at 4:50

Alexander Mills

1,885929

add a commentÂ |Â

draft saved

draft discarded

draft saved

draft discarded

Post as a guest

Name

sGVeYt7BPvQ,9LhI1,BEtqq,UPBuSEe bnqDDAHI gDoUBPceWod319v2QC4GUb,R3YB6pB0neeI7 dg,oh3mubv570QFB1F8VNy

搜尋此網誌

mjhjmtu