Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#69776 - [gcr] notice the user memlock limits have been modified on installation
Attached to Project:
Arch Linux
Opened by lilydjwg (lilydjwg) - Thursday, 25 February 2021, 08:09 GMT
Last edited by Jan Alexander Steffens (heftig) - Thursday, 25 February 2021, 19:42 GMT
Opened by lilydjwg (lilydjwg) - Thursday, 25 February 2021, 08:09 GMT
Last edited by Jan Alexander Steffens (heftig) - Thursday, 25 February 2021, 19:42 GMT
|
DetailsDescription:
The gcr package ships with a /etc/security/limits.d/10-gcr.conf that sets a 1024 memlock for the user. The intension here may be to raise the limit, but if the user has already set a higher limit (e.g. globally via systemd), this will lower it. So a notice is nice and easy to debug to users who care (instead of debugging by searching systemd issues and files, listing all processes' limits, etc). FYI I need a high memlock limit to run virtual machines with Intel GVT-g. Additional info: * package version(s) gcr 3.38.1-1 |
This task depends upon
Closed by Jan Alexander Steffens (heftig)
Thursday, 25 February 2021, 19:42 GMT
Reason for closing: Fixed
Thursday, 25 February 2021, 19:42 GMT
Reason for closing: Fixed
Comment by Jan Alexander Steffens (heftig) -
Thursday, 25 February 2021, 19:42 GMT
Added a message in trunk (will eventually appear at https://github.com/archlinux/svntogit-packages/commits/packages/gcr/trunk ); thanks.