On Sun, Feb 28, 2010 at 11:25:24AM +0100, Michael Andritschke wrote:
> The following message appears when starting jackd:
> 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 3046545
> I seem not to have such a file installed. Instead debconf has created
> /etc/security/limits.d/audio.conf which contains the given line.
Right. Everything as expected.
> If it wasn't for the fact that my changes there may get lost on the
> next update, I would suggest to just fix the notification message.
> Where am I supposed to change this setting?
The jackd package currently overwrites the file, that's right. This
should be fixed, because I'm treating debconf like a registry right now,
which is wrong.
> Second, if it is dangerous jackd shouldn't be configured by default
> with unlimited memory locking in the first place.
Unfortunately, it's not that easy. If you start ardour from the command
line, it complains if you have less than "unlimited". So either jackd or
ardour is unhappy.
Possible solution: don't start jackd and/or ardour from the
command line, so you don't see the messages. ;)
Or we could patch jackd to match ardour's limits.
However, we're currently more or less migrating to jackd2, and jackd2
doesn't contain such a message. Given that a user isn't affected by this
bug when starting jackd via qjackctl or his WM's menu and that jackd2
fixes it anyway, I'd simply leave it that way and fix the debconf issue.
Does this sound reasonable?
mail: a...@thur.de http://adi.thur.de PGP/GPG: key via keyserver
pkg-multimedia-maintainers mailing list