[arch-proaudio] package gcr breaks real-time settings

Ralf Mardorf ralf.mardorf at alice-dsl.net
Sun Sep 2 15:44:16 UTC 2018

Since arch general is under moderation, I forward a mail to this list.
Instead of shooting the developer/s who introduced the concept
of drop-in directories IMO an announcement would be appropriate.

Begin forwarded message:

Date: Sun, 2 Sep 2018 17:36:29 +0200
From: Ralf Mardorf <silver.bullet at zoho.com>
To: arch-general at archlinux.org
Subject: Re: [arch-general] users memlock value

On Sun, 2 Sep 2018 16:02:37 +0200, Ralf Mardorf wrote:
>On Sun, 2 Sep 2018 14:02:42 +0200, David Runge wrote:  
>>Also, please don't double post your issues. Give people time to
>>actually respond. No need to post to arch-general, if you brought this
>>up before. This is not an instant messenger service.    
>PS: Independent of what is required for a realtime (or the old audio)
>group and that there is no issue when using
>limits.d/file_with_a_higher_number.conf , I still question that
>'@users - memlock 1024' should be set by package. I doubt that a
>default 'memlock 1024' for the 'users' group is a good choice at all.  

PPS: And I forgot to mention, what Fons' pointed out and actually was
the issue that I experienced:

On Sun, 2 Sep 2018 16:55:49 +0200, Fons Adriaensen wrote:
>But that effectively means you need to opt out of whatever some
>'vendor' pushes down your throat. Not once, but everytime you update.  

The link to the complete message:

So at least an announcement via
https://lists.archlinux.org/listinfo/arch-announce should be considered.

pacman -Q linux{,-rt{-pussytoes,-cornflower,,-securityink}}|cut -d\  -f2

More information about the arch-proaudio mailing list