From: Ricardo Wurmus <rekado@elephly.net>
To: Jesse Gibbons <jgibbons2357@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: Help setting up ardour
Date: Sat, 31 Aug 2019 14:17:31 +0200 [thread overview]
Message-ID: <87d0glfs10.fsf@elephly.net> (raw)
In-Reply-To: <7ccec36fde6b49ae4057b9aa12e0f98e78c6e73d.camel@gmail.com>
Hi Jesse,
> under certain conditions; see the file COPYING for details
> JACK is running in realtime mode, but you are not allowed to use
> realtime scheduling.
> grep: /etc/security/limits.conf: No such file or directory
> Please check your /etc/security/limits.conf for the following line
> and correct/add it if necessary:
> @audio - rtprio 99
Why doesn’t /etc/security/limits.conf exist? Have you reconfigured your
system with the limits service that is suggested in the manual?
--
Ricardo
next prev parent reply other threads:[~2019-08-31 12:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-30 21:11 Help setting up ardour Jesse Gibbons
2019-08-31 12:17 ` Ricardo Wurmus [this message]
2019-08-31 15:35 ` Jesse Gibbons
2019-09-09 9:10 ` Ricardo Wurmus
2019-09-10 4:45 ` Jesse Gibbons
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d0glfs10.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=help-guix@gnu.org \
--cc=jgibbons2357@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).