Skip to content
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

Improve efficiency of code around the yum security updates by only calling the list once and parsing it #68

Open
swampdogmash opened this issue Apr 2, 2024 · 0 comments

Comments

@swampdogmash
Copy link
Contributor

Currently the security update check could take up to 50 seconds to complete, as it runs once to find out if the security update check is possible, then again to capture the info. This also prevents us from checking if any of the lines of output from the security update check as invalid (have seen instances where repos are broken and result in the counting of 2000+ error lines stating the security update is not available). By running the command once and caching the output in a file (or in a variable - paying attention to possible size of such variable and any limits)., it would be more efficient to execute the command once, and check for an error, but capture any non-error output for further assessment. This would be potentially twice as quick, and also permit error checking of the data returned.

@swampdogmash swampdogmash changed the title Improve efficiency of code around the um security updates by only calling the list once and parsing it Improve efficiency of code around the yum security updates by only calling the list once and parsing it Apr 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant