[ClusterLabs] Antw: [EXT] /etc/profile.d/which2.sh bug in RHEL/OL 8.5 can impact shell scripts
RHAYDEN at CERNER.COM
Mon Jan 31 08:32:16 EST 2022
> -----Original Message-----
> From: Users <users-bounces at clusterlabs.org> On Behalf Of Ulrich Windl
> Sent: Monday, January 31, 2022 2:01 AM
> To: users at clusterlabs.org
> Subject: [ClusterLabs] Antw: [EXT] /etc/profile.d/which2.sh bug in RHEL/OL
> 8.5 can impact shell scripts
> >>> "Hayden, Robert via Users" <users at clusterlabs.org> schrieb am
> 00:00 in Nachricht
> <DM6PR01MB5596D31A54575EBAEA4372ECD5239 at DM6PR01MB5596.prod.e
> é>1> Just an FYI ‑ there is a bug in /etc/profile.d/which2.sh script that
> > cause ksh scripts to fail. This impacted a Cluster when I upgraded to
> > Oracle Linux 8.5. We have a custom resource that calls a ksh script.
> > that ksh script we were sourcing /etc/profile. This in turn, sources the
> > /etc/profile.d/which2.sh script. The which2.sh script returned an error
> > that cascaded back through our Cluster Suite resource shell script causing
> > the node to evict. I downloaded Red Hat's proposed fix and that resolved
> > ksh script issues. I am hoping that Red Hat releases the correction for
> > RHEL 8.5.
> Out of curiosity: Can ksh do anything bash can't, or is it just the other way
> I haven't used ksh, but I switched from csh to bash once it had command
> history and editing.
> I never felt I need something different...
We are an old IBM/AIX shop, so some associates still like to code in korn shell. Habits die hard.
CONFIDENTIALITY NOTICE This message and any included attachments are from Cerner Corporation and are intended only for the addressee. The information contained in this message is confidential and may constitute inside or non-public information under international, federal, or state securities laws. Unauthorized forwarding, printing, copying, distribution, or use of such information is strictly prohibited and may be unlawful. If you are not the addressee, please promptly delete this message and notify the sender of the delivery error by e-mail or you may call Cerner's corporate offices in Kansas City, Missouri, U.S.A at (+1) (816)221-1024.
More information about the Users