Slackware64 14.0, real time kernel, no real time as user.
SlackwareThis Forum is for the discussion of Slackware Linux.
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.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
jackd has to run with realtime privileges. One way to do this on Slackware
would be to use set_rlimits. Since 12.2 there's another way - if you have
a filesystem that supports posix capabilities (reiserfs does not), you can
grant jackd the rights to run in realtime mode, even when started as a
normal user, with the following command:
I got this message for the following reasons when using set_rlimits:
- user was not in group "audio" (or whatever group was set in set_rlimits.conf)
- i missspelled the ablolute path to the program in set_rlimits.conf
- i didn't start the programm with "set_rlimits pgName"
WARNING: Your system has a limit for maximum amount of locked memory!
This might cause Ardour to run out of memory before your system runs
out of memory. You can view the memory limit with 'ulimit -l', and it
is normally controlled by /etc/security/limits.conf
You tried /sbin/initscript to set ulimit? Iirc, settings done via ulimit relate to the shell ulimit is run in: you have to do the change as root, but you will (hopefully) run ardour as user, so ardour won't be affectet by the new setting. Therefore this setting should be done in /sbin/initscript.
Edit: When you use set_rlimits you have to use /etc/set_rlimits.conf instead of /etc/security/limits.conf