Linux - NewbieThis forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Should I be ignoring this?, it says I can realtime: yes then continues to say, Real-time scheduling enabled in configuration but not allowed by policy
Code:
D: main.c: Started as real root: no, suid root: yes
I: main.c: PolicyKit grants us acquire-high-priority privilege.
I: main.c: PolicyKit grants us acquire-real-time privilege.
I: main.c: setrlimit(RLIMIT_NICE, (31, 31)) failed: Operation not permitted
I: main.c: setrlimit(RLIMIT_RTPRIO, (9, 9)) failed: Operation not permitted
D: main.c: Can realtime: yes, can high-priority: yes
I: main.c: Giving up CAP_NICE
I: main.c: Real-time scheduling enabled in configuration but not allowed by policy.
D: main.c: Can realtime: no, can high-priority: no
I: main.c: Daemon running as PID 4060
Hi, Do you have /etc/set_rlimits configured for the program you want to use?
/etc/set_rlimits.conf
Code:
# Configuration file for set_rlimits. Format is:
#
# name program max_nice_priority max_realtime_priority
# or
# name program <key>=<value> ...
#
# name is expected to be a username, a groupname if preceeded by a @ sign,
# or ALL (which matches all users). Negative priorities effectively
# disallow any setting of the respective priority for the matching entry.
# <key> can be rtprio, nice or memlock.
# Example entry:
#
# mark /usr/local/bin/jackd -1 80
#
# Here, user mark can execute /usr/local/bin/jackd using set_rlimits to set
# a realtime priority up to and including 80, but setting of a nice priority
# through set_rlimits is disallowed. Alternatively, if an `audio' group
# existed, the entry
#
# @audio /usr/local/bin/jackd -1 80
#
# would allow the same except the permission would extend to all members of
# the `audio' group. The same effect could be achieved with the key/value
# syntax:
#
# @audio /usr/local/bin/jackd nice=-1 rtprio=80
#
# For more details on the format and use of this file please refer to
# the set_rlimits manual page.
@audio /usr/bin/jackd nice=-1 rtprio=99 memlock=100000
@audio /usr/bin/qjackctl nice=-1 rtprio=99 memlock=100000
@audio /usr/bin/ardour nice=-1 rtprio=88 memlock=400000
#@audio /
@audio /usr/bin/fluidsynth nice=-1 rtprio=87 memlock=100000
@audio /usr/bin/hydrogen nice=-1 rtprio=86 memlock=100000
@audio /usr/bin/rosegarden nice=-1 rtprio=85 memlock=100000
@audio /usr/bin/vkeydb nice=-1 rtprio=84 memlock=100000
@audio /usr/bin/qsynth nice=-1 rtprio=83 memlock=100000
#audio /usr/bin/jackd nice=-1 rtprio=82 memlock=100000
Hashed (#)lines are commented out of the script (bash etc).
You will also need to make your "user" a member of the audio group.
Code:
chgrp --help
see my blog for install info and tute if required...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
Advertisement
Oracle Magazine contains technology strategy articles, sample code, tips, Oracle and partner news, how to articles for developers and DBAs, and more. Click Here to receive a complimentary subscription courtesy of LQ.