[pulseaudio-discuss] PulseAudio does not start with "lock-memory = yes" at boot

[Roman Beslik]

Well, I have 700 MB for that purposes (I run "mplayer" in locked memory):
{{{
$ cat /etc/security/limits.conf
@audio          -       memlock         700000
}}}
I need to find a test case which fails at boot as PulseAudio does.

On 12.02.12 17:31, Tanu Kaskinen wrote:
> On Fri, 2012-01-13 at 06:52 +0200, Roman Beslik wrote:
>> Hello.
>> I'm using ArchLinux. It runs "/etc/rc.local" at boot. If I start
>> PulseAudio with "lock-memory = yes" in "/etc/rc.local" with the line
>> {{{
>> sudo -u user env HOME=/home/user pulseaudio&
>> }}}
>> it yields an error:
>> {{{
>> shm.c: mmap() failed: Resource temporarily unavailable
>> core.c: failed to allocate shared memory pool. Falling back to a normal
>> memory pool.
>> shm.c: mmap() failed: Resource temporarily unavailable
>> core.c: pa_mempool_new() failed.
>> main.c: pa_core_new() failed.
>> }}}
>> But PulseAudio starts smoothly with the same configuration if I start it
>> from "bash".
>>
>> I tried to narrow a problem. My test program below runs smoothly from
>> "/etc/rc.local" and from "bash". What else can I test?
>
> Maybe the memlock resource limit (see "man limits.conf") is lower at
> boot than otherwise? That doesn't sound very likely, but I can't think
> of anything else... "ulimit -a" or "ulimit -l" can be used to find out
> the current limit in kilobytes from the command line.
>