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#2354 - change CONFIG_SECURITY_CAPABILITIES to module in kernel configuration
Attached to Project:
Arch Linux
Opened by Tobias Kieslich (tobias) - Friday, 11 March 2005, 18:29 GMT
Opened by Tobias Kieslich (tobias) - Friday, 11 March 2005, 18:29 GMT
|
DetailsChanging the CONFIG_SECURITY_CAPABILITIES form built in to module allows to compile and use realtime-lsm which you can find here:
http://www.justdreams.de/archlinux/downloads/realtime-lsm/ this module allows, when started with `modprobe realtime gid=92` to request realtime capabilities from the kernel for all users that are in the group 92 (audio). This is useful for any audio application that uses jack server. On the shortcoming side, the module capability isn't automatically loaded on request (you need it for vsftpd eg.) at least it failed for me and I have no clue where I can start to search. Dependend modules load it automatically, but for applications that need the capabilities the kernel doesn't do it automatically. Dunno how to handle it. |
This task depends upon
The problem is not realtime itself, the problem is that capability when built as module is not loaded by the kernel automatically when ann application needs it.
I hope I made it clear, If not we talk on IRC ;)
Thanks Scuba2deth
Thoughts?
If you have not realtime installed, a simple "modprobe capability" on startup solves the issue. If you have realtime-lsm installed "modprobe capability" asks for an argument and thus fails. So you have to type "modprobe realtime gid=92" instead of "modprobe capability". I dunno what kind of weird dependencies this are ...
realtime does not depend on capability it rather conflicts with it. Whenever one of them is loaded, modprobing the other fails with an "Invalid argument". Some further thoughts and possible workarounds are here:
http://bbs.archlinux.org/viewtopic.php?p=93658#93658