From: daniel-eys <daniel-eys@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: jack cannot use realtime scheduling
Date: Sun, 15 Mar 2020 02:30:55 +0100 [thread overview]
Message-ID: <20200315013055.Xi3H5PaU4Z37JztXlLFxIv8ktn_kY3KNI1byyHtCeb4@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: 659 bytes --]
New comment by daniel-eys on void-packages repository
https://github.com/void-linux/void-packages/issues/20051#issuecomment-599155763
Comment:
You're welcome, glad to hear that it works :)
My issue here is that I'm not really sure whether this is "the proper" fix to be included in the lightdm package. This was more like my first thought how it might work and it actually did.
For example, there is also polkit which handles `pam_limits`, maybe it's elogind's job to set session limits, `gdm` and `slim` add `session include system-local-login`, which (after some redirections) pulls in `pam_limits` via `system-auth`, I'm still a bit confused here.
prev parent reply other threads:[~2020-03-15 1:30 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
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 [this message]
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=20200315013055.Xi3H5PaU4Z37JztXlLFxIv8ktn_kY3KNI1byyHtCeb4@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).