View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0003042||ardour||bugs||public||2010-03-07 13:59||2010-04-15 18:12|
|Summary||0003042: limits.conf warnings inconsistent|
|Description||There are two ways to warn the user about his limits.conf settings, a popup (gtk2_ardour/ardour_ui.cc) and stdout.|
The popup appears if memlock is set to anything lower than 3/4 of the available memory.
stdout apparently warns whenever limits.conf is set to anything but unlimited, even if the number specified in limits.conf is equal to the total available memory.
It seems to simply check for 'unlimited' but I don't know where this code resides.
I think this should be consistent with the popup, whatever the correct figure might be.
|Additional Information||ardour 2.8.6 on Arch Linux, pure 64bit system.|
|Tags||No tags attached.|
||Can you attach the text that is printed on stdout?|
Sorry for the long delay:
WARNING: Your system has a limit for maximum amount of locked memory!
This might cause Ardour to run out of memory before your system runs
out of memory. You can view the memory limit with 'ulimit -l', and it
is normally controlled by /etc/security/limits.conf
$ ulimit -l
According to top my memory total is:
No idea where I got the above figure from..