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

Default RPM repo file sets expiry time too low #1060

Closed
cyqsimon opened this issue Nov 24, 2021 · 4 comments
Closed

Default RPM repo file sets expiry time too low #1060

cyqsimon opened this issue Nov 24, 2021 · 4 comments
Assignees
Labels
kind/enhancement New feature or request needs/triage

Comments

@cyqsimon
Copy link

This is an issue I posted over Gitter - so I'll simply paste it over:

I think the default RPM .repo file's metadata expiry is set too short. Currently it's 5 minutes which is entirely unnecessary. For reference the default value for dnf is 48 hours.
It becomes annoying during maintenance when I'm installing, uninstalling, querying, searching, updating, etc. packages with dnf. Basically any dnf command would trigger a metadata refresh for crowdsec. And as anyone who uses RHEL can tell you, updating repo metadata is often irritatingly slow.
It's not a difficult fix. I simply commented out metadata_expire=300 in /etc/yum.repos.d/crowdsec_crowdsec.repo and it reverts to the default 48h. But a more sensible default is always better IMO.

tl;dr

Make the default something more sensible, like 12h, or just remove the line to use the default 48h.

@cyqsimon cyqsimon added the kind/enhancement New feature or request label Nov 24, 2021
@LaurenceJJones
Copy link
Contributor

@sabban

Do we have access to this via our settings in packagecloud?

@sabban
Copy link
Contributor

sabban commented Mar 5, 2024

I believe we don't.

@sabban sabban closed this as completed Mar 5, 2024
@cyqsimon
Copy link
Author

cyqsimon commented Mar 6, 2024

Was this fixed? Or is this a "won't fix"?

@LaurenceJJones
Copy link
Contributor

Was this fixed? Or is this a "won't fix"?

Sorry it should of been placed under "wont fix" due to RPM time being out of our control within the installation script. If in the future we might have an external script for ourselves due to any/any requirements then we will have more control

@LaurenceJJones LaurenceJJones closed this as not planned Won't fix, can't repro, duplicate, stale Mar 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement New feature or request needs/triage
Projects
None yet
Development

No branches or pull requests

4 participants