27 May
2010
27 May
'10
9:22 p.m.
Hi all,
I updated to ubuntu 10.04 it asked me if I wanted a real-time kernel. I agreed. when I
start jack I get a warning:
Memory locking is unlimited - this is dangerous. You should probably alter the line:
@audio - memlock unlimited
in your /etc/limits.conf to read:
@audio - memlock 769515
I went to the limits.conf there was only:
@audio - rtpro-99 (or something similar). not
@audio - memlock unlimited
Under system administrator ubuntu studio controls there is a setting for memlock can I set
it there?
Because I have had a lock up already. And I'm not a Linux user I'm only setting up
a computer for some one who is and is not in the position to do it himself.
If it is better to set up from the command line please let me know.
__________ Information from ESET NOD32 Antivirus, version of virus signature database 5151
(20100527) __________
The message was checked by ESET NOD32 Antivirus.
http://www.eset.com
27 May
27 May
9:34 p.m.
Hey,
Adding the line:
@audio - memlock unlimited
should be safe enough. I've set up many systems, usually that does the trick
fine.
I have noticed that sometimes.. (seemingly quite random to me) some apps
(like Ardour)
would warn that "memlock is unlimited" and that could *cause* lock ups, and
it should be set
to something like "memlock 151832" or along those lines.. (Please dont use
that number, it totatlly
depends on how much RAM your system has, and how many apps your going to be
running etc etc)
Cheers, -Harry
WRT:
I updated to ubuntu 10.04 it asked me if I wanted a
real-time kernel. I
agreed. when I start jack I get a warning:
Memory locking is unlimited - this is dangerous. You should probably alter
the line:
@audio - memlock unlimited
in your /etc/limits.conf to read:
@audio - memlock 769515
9:51 p.m.
Hi
On 05/27/2010 09:34 PM, Harry Van Haaren wrote:
Hey,
Adding the line:
@audio - memlock unlimited
should be safe enough. I've set up many systems, usually that does the
trick fine.
I have noticed that sometimes.. (seemingly quite random to me) some
apps (like Ardour)
would warn that "memlock is unlimited" and that could *cause* lock
ups, and it should be set
to something like "memlock 151832" or along those lines.. (Please
dont use that number, it totatlly
depends on how much RAM your system has, and how many apps your going
to be running etc etc)
On Ubuntu Lucid the file /etc/security/limits.conf is no longer used for
this purpouse. Check the file /etc/security/limits.d/audio.conf instead.
I too had the same problem until I realized this.
From this link: http://ubuntustudio.org/LucidLynx -
Beginning with the Ubuntu package
jack-audio-connection-kit-0.118+svn3796-1ubuntu2 editing of
/etc/security/limits.conf should not be required. JACK will write the
following during post-installation to /etc/security/limits.d/audio.conf
# generated by jackd's postinst.
# Do not edit this file by hand, use
# dpkg-reconfigure -p high jack
# instead
@audio - rtprio 99
@audio - memlock unlimited
#@audio - nice -19
10:02 p.m.
Thanks for that Ailo,
Was aware that new JACK's had the .conf file seperate, havent used Ubuntu 10
at all yet, so I've no experience there.
Cheers, -Harry
From this link: http://ubuntustudio.org/LucidLynx -
10:19 p.m.
On Thu, May 27, 2010 at 9:22 PM, J. <jonathangoodman(a)bezeqint.net> wrote:
Hi all,
I updated to ubuntu 10.04 it asked me if I wanted a real-time kernel. I
agreed. when I start jack I get a warning:
Memory locking is unlimited - this is dangerous. You should probably alter
the line:
@audio - memlock unlimited
in your /etc/limits.conf to read:
@audio - memlock 769515
I went to the limits.conf there was only:
@audio - rtpro-99 (or something similar). not
@audio - memlock unlimited
Ailo wrote:
"JACK will write the following during post-installation to
/etc/security/limits.d/audio.conf
# generated by jackd's postinst.
# Do not edit this file by hand, use
# dpkg-reconfigure -p high jack
# instead
@audio - rtprio 99
@audio - memlock unlimited
#@audio - nice -19
"
"Beginning with the Ubuntu package
jack-audio-connection-kit-0.118+svn3796-1ubuntu2 editing of
/etc/security/limits.conf should not be required."
BUT:
ubuntustudio-audio metapackage has not yet deprecated this script that
writes:
@audio - rtprio 99
in
/etc/security/limits.conf
Under system administrator ubuntu studio controls
there is a setting for
memlock can I set it there?
Ubuntustudio-controls will write to /etc/security/limits.conf
Leave it alone and use the command line.
https://bugs.launchpad.net/ubuntustudio/+bug/571688
I think jack suggests 75% of your RAM memory. At least in my case, it was
exactly so. I suppose this is safer than "unlimited".
Cheers! Pablo
10:35 p.m.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Am 27.05.2010 20:19, schrieb Pablo Fernandez:
Ailo wrote:
"JACK will write the following during post-installation to
/etc/security/limits.d/audio.conf
Is there a special reason to change from the known method to write to
limits.conf to a all-new method to write to a file nobody seems to have
heared of before?
Is there any relese-note or such, where these reasons are discussed?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAkv+13sACgkQ1Aecwva1SWOcOACfbmHlTptJbh/54Rr7f1T2HUKJ
qhsAnimNmR74N7ND+ZdbLbvMWZDtmw9E
=mrGR
-----END PGP SIGNATURE-----
10:59 p.m.
On Thursday 27 May 2010 22:35:07 Hartmut Noack wrote:
Am 27.05.2010 20:19, schrieb Pablo Fernandez:
The "special" reason is:
If several packages modify one file, its very hard to track the changes. You
might want to purge packages with all their configuration later...
So its better if each package adds its own file to a directory and all these
files get parsed.
The same is done in /etc/apache2, in /etc/modprobe.d, in /etc/cron.[hourly|
daily|weekly|monthly] and many more. Its not a new and unknown method at all.
Have fun,
Arnold
Ailo wrote:
"JACK will write the following during post-installation to
/etc/security/limits.d/audio.conf
Is there a special reason to change from the known method to write to
limits.conf to a all-new method to write to a file nobody seems to have
heared of before?
Is there any relese-note or such, where these reasons are discussed?
5093
days inactive
5093
days old
linux-audio-user@lists.linuxaudio.org
6 comments
6 participants
participants (6)
-
ailo -
Arnold Krille -
Harry Van Haaren -
Hartmut Noack -
J. -
Pablo Fernandez