[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: gawk: sigpipe1.awk:7: fatal: print to "yes | true" failed: Broken pi
From: |
arnold |
Subject: |
Re: gawk: sigpipe1.awk:7: fatal: print to "yes | true" failed: Broken pipe |
Date: |
Wed, 13 Dec 2023 05:08:41 -0700 |
User-agent: |
Heirloom mailx 12.5 7/5/10 |
Andreas Schwab <schwab@suse.de> wrote:
> On Dez 12 2023, arnold@skeeve.com wrote:
>
> > It's inherently racy; the SIGPIPE handling is done around calls
> > to stdio's popen(), which does fork+exec. I just took a look at
> > the code and I don't see that there is anything else I can do.
>
> You could just use an empty signal handler, which is not inherited
> across exec.
I don't understand what you mean. Can you show me some code?
Thanks,
Arnold
- gawk: sigpipe1.awk:7: fatal: print to "yes | true" failed: Broken pipe, Andreas Schwab, 2023/12/11
- Re: gawk: sigpipe1.awk:7: fatal: print to "yes | true" failed: Broken pipe, arnold, 2023/12/11
- Re: gawk: sigpipe1.awk:7: fatal: print to "yes | true" failed: Broken pipe, arnold, 2023/12/11
- Re: gawk: sigpipe1.awk:7: fatal: print to "yes | true" failed: Broken pipe, Andreas Schwab, 2023/12/12
- Re: gawk: sigpipe1.awk:7: fatal: print to "yes | true" failed: Broken pipe, arnold, 2023/12/12
- Re: gawk: sigpipe1.awk:7: fatal: print to "yes | true" failed: Broken pipe, Andreas Schwab, 2023/12/12
- Re: gawk: sigpipe1.awk:7: fatal: print to "yes | true" failed: Broken pipe, arnold, 2023/12/12
- Re: gawk: sigpipe1.awk:7: fatal: print to "yes | true" failed: Broken pipe, Andreas Schwab, 2023/12/13
- Re: gawk: sigpipe1.awk:7: fatal: print to "yes | true" failed: Broken pipe,
arnold <=
- Re: gawk: sigpipe1.awk:7: fatal: print to "yes | true" failed: Broken pipe, Andreas Schwab, 2023/12/13
- Re: gawk: sigpipe1.awk:7: fatal: print to "yes | true" failed: Broken pipe, arnold, 2023/12/13
- Re: gawk: sigpipe1.awk:7: fatal: print to "yes | true" failed: Broken pipe, arnold, 2023/12/13