Hallo, hard off hat gesagt: // hard off wrote:
The rlimits approach will soon be common knowledge among all Linux
audio users anyway.
Not everyone wants to learn about this stuff. Some people just want to install Ubuntu Studio and make music.
hans, i am so much on your side here. ..although i'd say: 'some of us just want to install ubuntu studio, make massively complicated pd patches, and then make music.'
Others want to make massive 36-channel recordings with Ardour, run 128-voice synthesiziers with SuperCollider, rock the party with Mixxx, play Csound5 in realtime, edit midi arrangements with MusE, run a live webradio stream with icecast2 while OTOH others want to harden their webserver with port-knock logins or set fierce limits for all users. Should all these packages fight for who should edit limits.conf and whose edits will finally survive?
This is not about if users should learn how to edit limits.conf or not, this is about playing fair with other pieces of software installed in a distribution.
If it was only about making editing limits.conf easier, here's a way: Just run this script as root/under sudo:
#!/bin/sh if test -w /etc/security/limits.conf then read -p "Update /etc/security/limits.conf? [yN]: " DOIT if test "$DOIT" = "y" then echo "@audio - nice -10" >> /etc/security/limits.conf echo "@audio - rtprio 99" >> /etc/security/limits.conf echo "@audio - memlock unlimited" >> /etc/security/limits.conf echo "/etc/security/limits.conf updated successfully!" echo "You need to logout completely and login again to" echo "activate changes." echo "Also make sure you're in group "audio"." else echo "Okay, doing nothing" fi else echo "/etc/security/limits.conf not writable, giving up" fi
# EOF
Ciao
Frank Barknecht _ ______footils.org_ __goto10.org__