[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: bug in bash
From: |
Kerin Millar |
Subject: |
Re: bug in bash |
Date: |
Sun, 12 May 2024 09:42:49 +0100 |
On Sun, 12 May 2024 03:55:21 +0200
Quốc Trị Đỗ <quoctrijb@gmail.com> wrote:
> Hi,
>
> I found a bug when i tried with syntax <(cmd). this is an example
> cat <(wc -l) < bk
>
> You can follow this command, then you have bugs. I think because you
> created a fork getting inside in the parenthesis and the main process do <
> bk. They work parallel. Because of that, yeah.
> At least, I tried this here on this campus, at 42Heilbronn - Germany.
>
Let's replace wc with ps for a moment.
$ cat <(ps -j)
PID PGID SID TTY TIME CMD
7840 7840 7840 pts/0 00:00:00 bash
8492 7840 7840 pts/0 00:00:00 ps
8493 8493 7840 pts/0 00:00:00 cat
There, cat ends up being the sole member of the foreground process group (whose
PGID happened to be 8493 at the time). It can be seen that ps is not a member
of that same process group. Were ps to try to read from the standard input - as
wc does - it would also fail. The reason is that only processes belonging to
the foreground process group are allowed to read from the controlling terminal.
> How to fix it? It doesn't last that long. After a while, it will show "wc:
> stdin: read: Input/output error". Or we can ctrl C.
> Version 5.2
Though already asked, what were you intending for it to do?
--
Kerin Millar
- bug in bash, Quốc Trị Đỗ, 2024/05/12
- Re: bug in bash, Andreas Kähäri, 2024/05/12
- Re: bug in bash,
Kerin Millar <=
- Re: bug in bash, Greg Wooledge, 2024/05/12
- Re: bug in bash, Andreas Schwab, 2024/05/12
- Re: bug in bash, Oğuz, 2024/05/12
- Re: bug in bash, Chet Ramey, 2024/05/13
- Re: bug in bash, Oğuz, 2024/05/13
- Re: bug in bash, Chet Ramey, 2024/05/14
- Re: bug in bash, Andreas Schwab, 2024/05/14
- Re: bug in bash, Chet Ramey, 2024/05/14