Hi all,

lately I found that a bash script which uses a named pipe/FIFO for process substitution sometimes leaves /tmp/sh-np.<nnnnnn> files behind. This does not happen upon each invocation of the script, so it seems to be a race condition. It does only occur on systems that have the bash v5 RPM installed (5.1.4-2, to be more exact). On systems with the same AIX level (7200-05-04-2220) and bash v4 (4.3.30-1), the script runs without such remnants.

Here's a short example script to reproduce the problem:

#!/bin/bash
read min maj < <(uname -rv)
exec echo $maj $min

The exec command is what also matters here. Without that, there's also no such /tmp/sh-np.<nnnnnn> file afterwards. Sure enough in the real script this is used differently than in the example above, i.e. it invokes another command (perl in this case) that inherits some arguments and replaces the shell. Obviously when that happens, the named pipe/FIFO is not cleaned up correctly.

On a Linux system with bash v5 I don't see this behavior. So it appears to be specific to AIX and the bash v5 RPM for AIX.

BTW, there's another thread where this has already been discussed about a year ago, but there were no suggestions other than deleting these files afterwards. I'd rather see them not being left over, especially when the respective script is run frequently (via cron).

Any thoughts, comments or chances that this could be fixed? Thanks.

Regards,
Markus

This looks like " Bash-5.1 patch 8: clean up FIFOs created by redirections in child processes" (see https://git.savannah.gnu.org/cgit/bash.git/log/)

@SANKET RATHI - If you're going to update the bash package, you may want to include all patches up to 16.

​

------------------------------
José Pina Coelho
IT Specialist at Kyndryl
------------------------------

Original Message:
Sent: Thu June 23, 2022 06:41 AM
From: Markus Alt
Subject: Issue with bash v5 and named pipes/FIFOs

Hi all,

lately I found that a bash script which uses a named pipe/FIFO for process substitution sometimes leaves /tmp/sh-np.<nnnnnn> files behind. This does not happen upon each invocation of the script, so it seems to be a race condition. It does only occur on systems that have the bash v5 RPM installed (5.1.4-2, to be more exact). On systems with the same AIX level (7200-05-04-2220) and bash v4 (4.3.30-1), the script runs without such remnants.

Here's a short example script to reproduce the problem:

#!/bin/bash
read min maj < <(uname -rv)
exec echo $maj $min

The exec command is what also matters here. Without that, there's also no such /tmp/sh-np.<nnnnnn> file afterwards. Sure enough in the real script this is used differently than in the example above, i.e. it invokes another command (perl in this case) that inherits some arguments and replaces the shell. Obviously when that happens, the named pipe/FIFO is not cleaned up correctly.

On a Linux system with bash v5 I don't see this behavior. So it appears to be specific to AIX and the bash v5 RPM for AIX.

BTW, there's another thread where this has already been discussed about a year ago, but there were no suggestions other than deleting these files afterwards. I'd rather see them not being left over, especially when the respective script is run frequently (via cron).

Any thoughts, comments or chances that this could be fixed? Thanks.

Regards,
Markus

Right. We will update bash to the latest patch level (16).

------------------------------
Ayappan P
------------------------------

Original Message:
Sent: Fri June 24, 2022 07:26 AM
From: José Pina Coelho
Subject: Issue with bash v5 and named pipes/FIFOs

This looks like " Bash-5.1 patch 8: clean up FIFOs created by redirections in child processes" (see https://git.savannah.gnu.org/cgit/bash.git/log/)

@SANKET RATHI - If you're going to update the bash package, you may want to include all patches up to 16.

​

------------------------------
José Pina Coelho
IT Specialist at Kyndryl

Original Message:
Sent: Thu June 23, 2022 06:41 AM
From: Markus Alt
Subject: Issue with bash v5 and named pipes/FIFOs

Hi all,

lately I found that a bash script which uses a named pipe/FIFO for process substitution sometimes leaves /tmp/sh-np.<nnnnnn> files behind. This does not happen upon each invocation of the script, so it seems to be a race condition. It does only occur on systems that have the bash v5 RPM installed (5.1.4-2, to be more exact). On systems with the same AIX level (7200-05-04-2220) and bash v4 (4.3.30-1), the script runs without such remnants.

Here's a short example script to reproduce the problem:

#!/bin/bash
read min maj < <(uname -rv)
exec echo $maj $min

The exec command is what also matters here. Without that, there's also no such /tmp/sh-np.<nnnnnn> file afterwards. Sure enough in the real script this is used differently than in the example above, i.e. it invokes another command (perl in this case) that inherits some arguments and replaces the shell. Obviously when that happens, the named pipe/FIFO is not cleaned up correctly.

On a Linux system with bash v5 I don't see this behavior. So it appears to be specific to AIX and the bash v5 RPM for AIX.

BTW, there's another thread where this has already been discussed about a year ago, but there were no suggestions other than deleting these files afterwards. I'd rather see them not being left over, especially when the respective script is run frequently (via cron).

Any thoughts, comments or chances that this could be fixed? Thanks.

Regards,
Markus

This sounds in fact very much like it. Thank you for the pointer, José!
Original Message:
Sent: Fri June 24, 2022 07:26 AM
From: José Pina Coelho
Subject: Issue with bash v5 and named pipes/FIFOs

This looks like " Bash-5.1 patch 8: clean up FIFOs created by redirections in child processes" (see https://git.savannah.gnu.org/cgit/bash.git/log/)

@SANKET RATHI - If you're going to update the bash package, you may want to include all patches up to 16.

​

------------------------------
José Pina Coelho
IT Specialist at Kyndryl

Original Message:
Sent: Thu June 23, 2022 06:41 AM
From: Markus Alt
Subject: Issue with bash v5 and named pipes/FIFOs

Hi all,

lately I found that a bash script which uses a named pipe/FIFO for process substitution sometimes leaves /tmp/sh-np.<nnnnnn> files behind. This does not happen upon each invocation of the script, so it seems to be a race condition. It does only occur on systems that have the bash v5 RPM installed (5.1.4-2, to be more exact). On systems with the same AIX level (7200-05-04-2220) and bash v4 (4.3.30-1), the script runs without such remnants.

Here's a short example script to reproduce the problem:

#!/bin/bash
read min maj < <(uname -rv)
exec echo $maj $min

The exec command is what also matters here. Without that, there's also no such /tmp/sh-np.<nnnnnn> file afterwards. Sure enough in the real script this is used differently than in the example above, i.e. it invokes another command (perl in this case) that inherits some arguments and replaces the shell. Obviously when that happens, the named pipe/FIFO is not cleaned up correctly.

On a Linux system with bash v5 I don't see this behavior. So it appears to be specific to AIX and the bash v5 RPM for AIX.

BTW, there's another thread where this has already been discussed about a year ago, but there were no suggestions other than deleting these files afterwards. I'd rather see them not being left over, especially when the respective script is run frequently (via cron).

Any thoughts, comments or chances that this could be fixed? Thanks.

Regards,
Markus

Thank you Jose. We will update bash to include all these patches.

------------------------------
SANKET RATHI
------------------------------

Original Message:
Sent: Fri June 24, 2022 07:26 AM
From: José Pina Coelho
Subject: Issue with bash v5 and named pipes/FIFOs

This looks like " Bash-5.1 patch 8: clean up FIFOs created by redirections in child processes" (see https://git.savannah.gnu.org/cgit/bash.git/log/)

@SANKET RATHI - If you're going to update the bash package, you may want to include all patches up to 16.

​

------------------------------
José Pina Coelho
IT Specialist at Kyndryl

Original Message:
Sent: Thu June 23, 2022 06:41 AM
From: Markus Alt
Subject: Issue with bash v5 and named pipes/FIFOs

Hi all,

lately I found that a bash script which uses a named pipe/FIFO for process substitution sometimes leaves /tmp/sh-np.<nnnnnn> files behind. This does not happen upon each invocation of the script, so it seems to be a race condition. It does only occur on systems that have the bash v5 RPM installed (5.1.4-2, to be more exact). On systems with the same AIX level (7200-05-04-2220) and bash v4 (4.3.30-1), the script runs without such remnants.

Here's a short example script to reproduce the problem:

#!/bin/bash
read min maj < <(uname -rv)
exec echo $maj $min

The exec command is what also matters here. Without that, there's also no such /tmp/sh-np.<nnnnnn> file afterwards. Sure enough in the real script this is used differently than in the example above, i.e. it invokes another command (perl in this case) that inherits some arguments and replaces the shell. Obviously when that happens, the named pipe/FIFO is not cleaned up correctly.

On a Linux system with bash v5 I don't see this behavior. So it appears to be specific to AIX and the bash v5 RPM for AIX.

BTW, there's another thread where this has already been discussed about a year ago, but there were no suggestions other than deleting these files afterwards. I'd rather see them not being left over, especially when the respective script is run frequently (via cron).

Any thoughts, comments or chances that this could be fixed? Thanks.

Regards,
Markus

Any outlook when an updated bash RPM will be made available? Thanks.
Original Message:
Sent: Fri June 24, 2022 01:17 PM
From: SANKET RATHI
Subject: Issue with bash v5 and named pipes/FIFOs

Thank you Jose. We will update bash to include all these patches.

------------------------------
SANKET RATHI

Original Message:
Sent: Fri June 24, 2022 07:26 AM
From: José Pina Coelho
Subject: Issue with bash v5 and named pipes/FIFOs

This looks like " Bash-5.1 patch 8: clean up FIFOs created by redirections in child processes" (see https://git.savannah.gnu.org/cgit/bash.git/log/)

@SANKET RATHI - If you're going to update the bash package, you may want to include all patches up to 16.

​

------------------------------
José Pina Coelho
IT Specialist at Kyndryl

Original Message:
Sent: Thu June 23, 2022 06:41 AM
From: Markus Alt
Subject: Issue with bash v5 and named pipes/FIFOs

Hi all,

lately I found that a bash script which uses a named pipe/FIFO for process substitution sometimes leaves /tmp/sh-np.<nnnnnn> files behind. This does not happen upon each invocation of the script, so it seems to be a race condition. It does only occur on systems that have the bash v5 RPM installed (5.1.4-2, to be more exact). On systems with the same AIX level (7200-05-04-2220) and bash v4 (4.3.30-1), the script runs without such remnants.

Here's a short example script to reproduce the problem:

#!/bin/bash
read min maj < <(uname -rv)
exec echo $maj $min

The exec command is what also matters here. Without that, there's also no such /tmp/sh-np.<nnnnnn> file afterwards. Sure enough in the real script this is used differently than in the example above, i.e. it invokes another command (perl in this case) that inherits some arguments and replaces the shell. Obviously when that happens, the named pipe/FIFO is not cleaned up correctly.

On a Linux system with bash v5 I don't see this behavior. So it appears to be specific to AIX and the bash v5 RPM for AIX.

BTW, there's another thread where this has already been discussed about a year ago, but there were no suggestions other than deleting these files afterwards. I'd rather see them not being left over, especially when the respective script is run frequently (via cron).

Any thoughts, comments or chances that this could be fixed? Thanks.

Regards,
Markus

We are targeting end of this month.

------------------------------
SANKET RATHI
------------------------------

Original Message:
Sent: Wed September 14, 2022 06:15 AM
From: Markus Alt
Subject: Issue with bash v5 and named pipes/FIFOs

Any outlook when an updated bash RPM will be made available? Thanks.
Original Message:
Sent: Fri June 24, 2022 01:17 PM
From: SANKET RATHI
Subject: Issue with bash v5 and named pipes/FIFOs

Thank you Jose. We will update bash to include all these patches.

------------------------------
SANKET RATHI

Original Message:
Sent: Fri June 24, 2022 07:26 AM
From: José Pina Coelho
Subject: Issue with bash v5 and named pipes/FIFOs

This looks like " Bash-5.1 patch 8: clean up FIFOs created by redirections in child processes" (see https://git.savannah.gnu.org/cgit/bash.git/log/)

@SANKET RATHI - If you're going to update the bash package, you may want to include all patches up to 16.

​

------------------------------
José Pina Coelho
IT Specialist at Kyndryl

Original Message:
Sent: Thu June 23, 2022 06:41 AM
From: Markus Alt
Subject: Issue with bash v5 and named pipes/FIFOs

Hi all,

lately I found that a bash script which uses a named pipe/FIFO for process substitution sometimes leaves /tmp/sh-np.<nnnnnn> files behind. This does not happen upon each invocation of the script, so it seems to be a race condition. It does only occur on systems that have the bash v5 RPM installed (5.1.4-2, to be more exact). On systems with the same AIX level (7200-05-04-2220) and bash v4 (4.3.30-1), the script runs without such remnants.

Here's a short example script to reproduce the problem:

#!/bin/bash
read min maj < <(uname -rv)
exec echo $maj $min

The exec command is what also matters here. Without that, there's also no such /tmp/sh-np.<nnnnnn> file afterwards. Sure enough in the real script this is used differently than in the example above, i.e. it invokes another command (perl in this case) that inherits some arguments and replaces the shell. Obviously when that happens, the named pipe/FIFO is not cleaned up correctly.

On a Linux system with bash v5 I don't see this behavior. So it appears to be specific to AIX and the bash v5 RPM for AIX.

BTW, there's another thread where this has already been discussed about a year ago, but there were no suggestions other than deleting these files afterwards. I'd rather see them not being left over, especially when the respective script is run frequently (via cron).

Any thoughts, comments or chances that this could be fixed? Thanks.

Regards,
Markus

Ok, great! Thank you, Sanket!
Original Message:
Sent: Fri September 16, 2022 06:38 AM
From: SANKET RATHI
Subject: Issue with bash v5 and named pipes/FIFOs

We are targeting end of this month.

------------------------------
SANKET RATHI

Original Message:
Sent: Wed September 14, 2022 06:15 AM
From: Markus Alt
Subject: Issue with bash v5 and named pipes/FIFOs

Any outlook when an updated bash RPM will be made available? Thanks.
Original Message:
Sent: Fri June 24, 2022 01:17 PM
From: SANKET RATHI
Subject: Issue with bash v5 and named pipes/FIFOs

Thank you Jose. We will update bash to include all these patches.

------------------------------
SANKET RATHI

Original Message:
Sent: Fri June 24, 2022 07:26 AM
From: José Pina Coelho
Subject: Issue with bash v5 and named pipes/FIFOs

This looks like " Bash-5.1 patch 8: clean up FIFOs created by redirections in child processes" (see https://git.savannah.gnu.org/cgit/bash.git/log/)

@SANKET RATHI - If you're going to update the bash package, you may want to include all patches up to 16.

​

------------------------------
José Pina Coelho
IT Specialist at Kyndryl

Original Message:
Sent: Thu June 23, 2022 06:41 AM
From: Markus Alt
Subject: Issue with bash v5 and named pipes/FIFOs

Hi all,

lately I found that a bash script which uses a named pipe/FIFO for process substitution sometimes leaves /tmp/sh-np.<nnnnnn> files behind. This does not happen upon each invocation of the script, so it seems to be a race condition. It does only occur on systems that have the bash v5 RPM installed (5.1.4-2, to be more exact). On systems with the same AIX level (7200-05-04-2220) and bash v4 (4.3.30-1), the script runs without such remnants.

Here's a short example script to reproduce the problem:

#!/bin/bash
read min maj < <(uname -rv)
exec echo $maj $min

The exec command is what also matters here. Without that, there's also no such /tmp/sh-np.<nnnnnn> file afterwards. Sure enough in the real script this is used differently than in the example above, i.e. it invokes another command (perl in this case) that inherits some arguments and replaces the shell. Obviously when that happens, the named pipe/FIFO is not cleaned up correctly.

On a Linux system with bash v5 I don't see this behavior. So it appears to be specific to AIX and the bash v5 RPM for AIX.

BTW, there's another thread where this has already been discussed about a year ago, but there were no suggestions other than deleting these files afterwards. I'd rather see them not being left over, especially when the respective script is run frequently (via cron).

Any thoughts, comments or chances that this could be fixed? Thanks.

Regards,
Markus