Description of problem:
Initscripts prior to 10.03 has a bug when used with grep 3.2 or newer.
CentOS 8 and RHEL 8 are using initscripts 10.00.6 and grep 3.1, but some users choose to upgrade to a newer version of grep on their own and hit this bug. This will also be a problem if RHEL chooses to rebase grep or backport that behavior in the future.
Version-Release number of selected component (if applicable):
The community has offered a backport already.
Please disregard that last link in the additional info. That's a patch that would apply to the CentOS initscripts package source, not to the initscripts source itself. The appropriate patch to apply in the RHEL spec file would be the upstream one.
thank you, I completely forgot about this issue. I'll backport it from upstream. I should make it into RHEL 8.3.0.
Upstream PR: https://github.com/fedora-sysv/initscripts/pull/317
Any update on this? fwiw I had a chat with grep upstream and they've confirmed the PR will properly mitigate this issue.
(In reply to Davide Cavalca from comment #5)
> Any update on this? fwiw I had a chat with grep upstream and they've
> confirmed the PR will properly mitigate this issue.
The fix is planned for 8.3.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (initscripts bug fix and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.