tail: error writing 'standard output': Broken pipe

The name of the pictureThe name of the pictureThe name of the pictureClash 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,










share|improve this question

















  • 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














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,










share|improve this question

















  • 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












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,










share|improve this question













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






share|improve this question













share|improve this question











share|improve this question




share|improve this question










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. 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












  • 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







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















active

oldest

votes











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: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
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%2f481174%2ftail-error-writing-standard-output-broken-pipe%23new-answer', 'question_page');

);

Post as a guest



































active

oldest

votes













active

oldest

votes









active

oldest

votes






active

oldest

votes















 

draft saved


draft discarded















































 


draft saved


draft discarded














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













































































Popular posts from this blog

How to check contact read email or not when send email to Individual?

Bahrain

Postfix configuration issue with fips on centos 7; mailgun relay