-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
fedora 40 bug on detecting systemd-analyze version #1525
Comments
Issue opened with no description? Can you elaborate a bit? |
try this, you will see 9 places where a slosh (backslash) preceeds a - (minus)
previously a number of these "errors" occured, but on FC40 it's down to one. I guess that if there is still a version of grep out there that requires "-" escaped by "" |
Sorry that should have been, |
Version in fedora40 is, |
Once fixed we have to try to persuade the packager to include it in the next release or |
think it is fixed in fedora 40. |
Is this still an issue or resolved? |
In version lynis.noarch 3.1.1-1.fc40 @fedora I still see one instance of,
emanating from lynis. I am assuming 312 will get into FC40 soon, but it it's not as of this moment. I'll try to resist commenting on systemd! It reminds me of the Monty Python "abuse" sketch. |
The question is why does awk fail in the command below. It gives an error message.
I already posted this. It seems someone has deleted it so I will post it again.
I run this script from /etc/cron.daily
The cron job gives the error:
ANSWER / SOLUTION / FIX
in /usr/share/lynis/include there is a file tests_boot_services which does not detect SYSTEMD_VERSION on my system correctly. So I fixed it by brute force:
using the rpm version the awk command fails so I just manually overrided SYSTEMD_VERSION.
The text was updated successfully, but these errors were encountered: