tail: error writing 'standard output': Broken pipe

Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
I tried to use some scripts which use tail commands on Debian stretch but I got tail: error writing 'standard output': Broken pipe.
Does Debian handle tail and pipe syntax differently?
Thank you in advance,
debian pipe tail
add a comment |
up vote
0
down vote
favorite
I tried to use some scripts which use tail commands on Debian stretch but I got tail: error writing 'standard output': Broken pipe.
Does Debian handle tail and pipe syntax differently?
Thank you in advance,
debian pipe tail
1
You probably have the SIGPIPE signal handler set to 'ignore' in your script or in another program calling it (eg. withtrap '' PIPE). Don't do that.
– mosvy
6 hours ago
I checked the code but it appears there noSIGPIPE.
– user977828
6 hours ago
Your code, for exampletail -c +$index[$contig] $fasta | awk '$0~/>/exit1'specifically breaks the pipe in certain situations -- just to make that clear. If you can't control the SIGPIPE handling, then you may want to rework the code so that it tests for the/>/condition before calling the pipeline.
– Jeff Schaller
5 hours ago
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I tried to use some scripts which use tail commands on Debian stretch but I got tail: error writing 'standard output': Broken pipe.
Does Debian handle tail and pipe syntax differently?
Thank you in advance,
debian pipe tail
I tried to use some scripts which use tail commands on Debian stretch but I got tail: error writing 'standard output': Broken pipe.
Does Debian handle tail and pipe syntax differently?
Thank you in advance,
debian pipe tail
debian pipe tail
asked 7 hours ago
user977828
3451516
3451516
1
You probably have the SIGPIPE signal handler set to 'ignore' in your script or in another program calling it (eg. withtrap '' PIPE). Don't do that.
– mosvy
6 hours ago
I checked the code but it appears there noSIGPIPE.
– user977828
6 hours ago
Your code, for exampletail -c +$index[$contig] $fasta | awk '$0~/>/exit1'specifically breaks the pipe in certain situations -- just to make that clear. If you can't control the SIGPIPE handling, then you may want to rework the code so that it tests for the/>/condition before calling the pipeline.
– Jeff Schaller
5 hours ago
add a comment |
1
You probably have the SIGPIPE signal handler set to 'ignore' in your script or in another program calling it (eg. withtrap '' PIPE). Don't do that.
– mosvy
6 hours ago
I checked the code but it appears there noSIGPIPE.
– user977828
6 hours ago
Your code, for exampletail -c +$index[$contig] $fasta | awk '$0~/>/exit1'specifically breaks the pipe in certain situations -- just to make that clear. If you can't control the SIGPIPE handling, then you may want to rework the code so that it tests for the/>/condition before calling the pipeline.
– Jeff Schaller
5 hours ago
1
1
You probably have the SIGPIPE signal handler set to 'ignore' in your script or in another program calling it (eg. with
trap '' PIPE). Don't do that.– mosvy
6 hours ago
You probably have the SIGPIPE signal handler set to 'ignore' in your script or in another program calling it (eg. with
trap '' PIPE). Don't do that.– mosvy
6 hours ago
I checked the code but it appears there no
SIGPIPE.– user977828
6 hours ago
I checked the code but it appears there no
SIGPIPE.– user977828
6 hours ago
Your code, for example
tail -c +$index[$contig] $fasta | awk '$0~/>/exit1' specifically breaks the pipe in certain situations -- just to make that clear. If you can't control the SIGPIPE handling, then you may want to rework the code so that it tests for the />/ condition before calling the pipeline.– Jeff Schaller
5 hours ago
Your code, for example
tail -c +$index[$contig] $fasta | awk '$0~/>/exit1' specifically breaks the pipe in certain situations -- just to make that clear. If you can't control the SIGPIPE handling, then you may want to rework the code so that it tests for the />/ condition before calling the pipeline.– Jeff Schaller
5 hours ago
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f481174%2ftail-error-writing-standard-output-broken-pipe%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
1
You probably have the SIGPIPE signal handler set to 'ignore' in your script or in another program calling it (eg. with
trap '' PIPE). Don't do that.– mosvy
6 hours ago
I checked the code but it appears there no
SIGPIPE.– user977828
6 hours ago
Your code, for example
tail -c +$index[$contig] $fasta | awk '$0~/>/exit1'specifically breaks the pipe in certain situations -- just to make that clear. If you can't control the SIGPIPE handling, then you may want to rework the code so that it tests for the/>/condition before calling the pipeline.– Jeff Schaller
5 hours ago