-
Notifications
You must be signed in to change notification settings - Fork 237
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
hwclock init script logging grep warning #548
Comments
normally we'd use |
Oh, sure, I'll create a PR |
particleflux
added a commit
to particleflux/openrc
that referenced
this issue
Sep 7, 2022
Starting with grep version 3.8, the hwclock init script logs warnings about stray backslashes: > hwclock | * Setting system clock using the hardware clock [UTC] ... > hwclock |grep: warning: stray \ before - > hwclock |grep: warning: stray \ before - This is caused by the check for existence of the `--noadjfile` argument in function `get_noadjfile()`. Replacing the affected logic with an explicit argument denoting the pattern as such resolves the issue. Fixes OpenRC#548
vapier
pushed a commit
that referenced
this issue
Sep 7, 2022
Starting with grep version 3.8, the hwclock init script logs warnings about stray backslashes: > hwclock | * Setting system clock using the hardware clock [UTC] ... > hwclock |grep: warning: stray \ before - > hwclock |grep: warning: stray \ before - This is caused by the check for existence of the `--noadjfile` argument in function `get_noadjfile()`. Replacing the affected logic with an explicit argument denoting the pattern as such resolves the issue. Fixes #548
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
With the latest
grep
(3.8), thehwclock
init script throws a warning on start in the logic to detect--noadjfile
argument support:openrc/init.d/hwclock.in
Lines 74 to 75 in 112b698
This seems to have been introduced in
grep
in this commit: https://git.savannah.gnu.org/cgit/grep.git/commit/?id=e7f8e8eb1fd41b308ee10741bbd8068acc1847c2I think replacing the affected logic with
should work.
The text was updated successfully, but these errors were encountered: