2009/11/21 cal <span dir="ltr"><<a href="mailto:cal@graggrag.com">cal@graggrag.com</a>></span><br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Der Mickster wrote:<br>
> Hey,<br>
><br>
> Can't seem to start jackd in realtime as user on ubuntu studio. It<br>
> does start as root, but that's hardly a consolation (unless I run all<br>
> audio software as root, which would be kinda daft IMO)<br>
><br>
> @audio - rtprio 99<br>
> @audio - nice -10<br>
> @audio - memlock unlimited<br>
><br>
> have been added to /etc/security/limits.conf<br>
><br>
> Nevertheless, starting it as user just doesn't seem to work, and I<br>
> just can't figure out why. I've googled the issue, and everybody seems<br>
> to agree that modifying limits.conf in the above manner should solve<br>
> the problem - yet this is what I get:<br>
><br>
><br>
> mick@kaizoku:~$ jackd -R -P89 -dalsa -dhw:0 -r48000 -p256 -n3 -S &<br>
> [1] 3092<br>
> mick@kaizoku:~$ no message buffer overruns<br>
> jackd 0.116.1<br>
> Copyright 2001-2005 Paul Davis and others.<br>
> jackd comes with ABSOLUTELY NO WARRANTY<br>
> This is free software, and you are welcome to redistribute it<br>
> under certain conditions; see the file COPYING for details<br>
><br>
> JACK compiled with System V SHM support.<br>
> cannot use real-time scheduling (FIFO at priority 10) [for thread<br>
> -1217255744, from thread -1217255744] (1: Operation not permitted)<br>
> cannot create engine<br>
><br>
> Any ideas?<br>
<br>
Not sure if this is a possible answer to the question, or perhaps another<br>
question altogether, but ... I've struggled with the same issue on a debian<br>
system for some time, then discovered this in /etc/pam.d/su -<br>
<br>
# Sets up user limits, please uncomment and read /etc/security/limits.conf<br>
# to enable this functionality.<br>
# (Replaces the use of /etc/limits in old login)<br>
# session required pam_limits.so<br>
<br>
So far, I'm still not sure if uncommenting the 'session required pam_limits.so'<br>
line actually solves the problem, but I am curious.<br>
<br>
cheers.<br>
<br>
(I dumbly sent this to just the op instead of 'reply all', so fwiw I'm repeating<br>
it to the list)<br>
_______________________________________________<br>
Linux-audio-user mailing list<br>
<a href="mailto:Linux-audio-user@lists.linuxaudio.org">Linux-audio-user@lists.linuxaudio.org</a><br>
<a href="http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user" target="_blank">http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user</a><br>
</blockquote></div><br><div>Yes, that one is only when you do not use a PAM-enabled login, i.e you log in via VC. Probably 4/5 login managers are PAM-enabled, or maybe even 5/5.</div>