[MDEV-9095] [PATCH] systemd capability for --memlock Created: 2015-11-07 Updated: 2024-01-23 Resolved: 2024-01-19 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Packaging |
| Affects Version/s: | 10.1.8 |
| Fix Version/s: | 10.1.10 |
| Type: | Bug | Priority: | Major |
| Reporter: | Daniel Black | Assignee: | Sergey Vojtovich |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | patch, systemd | ||
| Issue Links: |
|
||||||||||||
| Sprint: | 10.1.9-3, 10.1.10 | ||||||||||||
| Description |
|
As mentioned by serg in MDEV8995 comment 77779 memlock can't be achieved in system configuration because of running as User=mysql Referenced patch reworks implementation to expose capability IPC_LOCK to allow the unpriv mysql to achieve this functionality. |
| Comments |
| Comment by Daniel Black [ 2015-11-07 ] |
|
patch as per github pull request 117 |
| Comment by Sergey Vojtovich [ 2015-12-22 ] |
|
serg, please review fix for this bug. |
| Comment by Sergey Vojtovich [ 2015-12-22 ] |
|
...second version of patch |
| Comment by Hartmut Holzgraefe [ 2024-01-19 ] |
|
This does not seem to work for me with 10.6.16 (on Rocky Linux 9) The mariadb.service file clearly has CapabilityBoundingSet=CAP_IPC_LOCK CAP_DAC_OVERRIDE CAP_AUDIT_WRITE but when requesting memlock in the configuration I'm still getting [Warning] Failed to lock memory. Errno: 12 |
| Comment by Sergei Golubchik [ 2024-01-19 ] |
|
please, report a new issue |