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 serv
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 (o
On Sun, 2 Sep 2018 14:02:42 +0200, David Runge wrote:
>Guess we can safely file this under "misconfiguration"?
Yes!
Ass already pointed out by
https://lists.archlinux.org/pipermail/arch-general/2018-September/045550.html
(and for detailed explanation why this happened
https://lists.archlinux.or
On 2018-09-02 12:14:51 (+0200), Ralf Mardorf wrote:
> I wonder if it's reasonable, that a package sets an '@users - memlock'
> value, since it overrides needed memlock values of other groups.
Guess we can safely file this under "misconfiguration"?
https://lists.archlinux.org/pipermail/arch-proaudio
On Sun, 2 Sep 2018 12:14:51 +0200, Ralf Mardorf wrote:
>I wonder if it's reasonable, that a package sets an
>'@users - memlock' value, since it overrides needed memlock values of
>other groups.
>
>[rocketmouse@archlinux ~]$ cat /etc/security/limits.d/10-gcr.conf
>@users - memlock 1024
>
># vim:set
5 matches
Mail list logo
