From: daniel-eys <daniel-eys@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: jack cannot use realtime scheduling
Date: Sat, 14 Mar 2020 02:12:07 +0100 [thread overview]
Message-ID: <20200314011207.ql7zAdRPNhiZmnq00ppsCHSLNbtX2a15Oy0ldHsWdHc@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-20051@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 448 bytes --]
New comment by daniel-eys on void-packages repository
https://github.com/void-linux/void-packages/issues/20051#issuecomment-598990967
Comment:
Right, this restricts the group `users` to limit memlock to 1024KB.
But you said your memlock limit is still at 64. (which is definitely the issue here)
I'm not really sure why jack.conf is not properly picked up and setting memlock to unlimited. :/
Are you able to manually `ulimit -l unlimited`?
next prev parent reply other threads:[~2020-03-14 1:12 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-12 21:44 [ISSUE] " VoidDuck
2020-03-13 14:47 ` VoidDuck
2020-03-13 16:59 ` daniel-eys
2020-03-13 17:13 ` VoidDuck
2020-03-13 17:22 ` daniel-eys
2020-03-13 19:41 ` jrigg
2020-03-13 19:43 ` jrigg
2020-03-13 22:16 ` VoidDuck
2020-03-13 22:16 ` VoidDuck
2020-03-13 22:37 ` daniel-eys
2020-03-13 22:57 ` VoidDuck
2020-03-13 23:45 ` daniel-eys
2020-03-13 23:47 ` daniel-eys
2020-03-13 23:50 ` daniel-eys
2020-03-13 23:52 ` daniel-eys
2020-03-13 23:56 ` VoidDuck
2020-03-13 23:56 ` VoidDuck
2020-03-14 1:12 ` daniel-eys [this message]
2020-03-14 9:12 ` VoidDuck
2020-03-14 16:19 ` daniel-eys
2020-03-14 18:07 ` VoidDuck
2020-03-14 23:18 ` VoidDuck
2020-03-14 23:18 ` [ISSUE] [CLOSED] " VoidDuck
2020-03-14 23:37 ` daniel-eys
2020-03-14 23:51 ` VoidDuck
2020-03-15 1:30 ` daniel-eys
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200314011207.ql7zAdRPNhiZmnq00ppsCHSLNbtX2a15Oy0ldHsWdHc@z \
--to=daniel-eys@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/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 NNTP newsgroup(s).