-
Notifications
You must be signed in to change notification settings - Fork 363
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
Adding implementation for runlevel probe on SUSE #369
Conversation
Can one of the admins verify this patch? |
Test this please (message for our jenkins) 🛀 |
@GautamSatish Thanks for your contribution. I don't like that most of the code is a copy from |
@jan-cerny , forgive me, you had already given me this comment on the mailing list, it slipped my mind. I can add a wrapper to the Or, I could add a new define option in CFLAGS say -D_SUSE=0 and the value needs to be set to 1 when building for SUSE so that we can simply add What do you think? |
@GautamSatish First option sounds better to me. |
@jan-cerny , I have made the modifications in the second commit. Could you please take a look? |
@GautamSatish Thanks! Now the code looks good to me, Please squash the two commits, do |
Updated the runlevel probe with some refactoring.
48ba3a8
to
ebe4880
Compare
@jan-cerny I think I have merged the way you wanted. |
@GautamSatish Thank you very much. We highly appreciate all efforts that make OpenSCAP usable on other platforms. There are still some minor issues in your code -- an unused variable in |
This check-in implements the run-level probe for SUSE as was discussed on the mailing list.
If have implemented the function separate from get_runlevel_sysv because the file paths to init.d and the rc directories are different on SUSE and there was no GCC macros to distinguish between RHEL and SUSE.
Also included the linux/limits.h header file in oval_session.c to resolve PATH_MAX.