This is again not a subject for this bug, but could perhaps be a small
addition to the jack-common package?
There has been some concern whether using memlock unlimited is safe, but
in order to know what to set it to, for instance 95% of the memory size,
you would first need to check the memory size, and then replace the
value in the .conf file.
I don't know where such a script could live, but I assume somewhere in
the early boot process.
Even just doing it once is probably not a good idea, since people add
and remove memory now and again. Don't what implications there would be
if the memory size is smaller than what is written in the conf file.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
