[SOLVED] Slackware64 14.2. User '1000' does not exist
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
The first part works, but the second part returns:
Code:
# usermod -a -G realtime 1000
usermod: user '1000' does not exist
.
However, when I run:
Code:
# id -u username
1000
I am trying to do this as the result of a problem in Ardour 5. A thread recommends the following:
Quote:
Your system is not configured for real time scheduling. You are using JACK2, which refuses to start if realtime scheduling does not work.
Fix your system configuration and it will work again. Alternatively, use the ALSA backend to Ardour. You should fix your system, because Ardour needs RT scheduling no matter which audio/MIDI backend it uses.
Thanks for the reply. Unfortunately, I still have the Ardour 5 "could not create session" problem.
I think you missed the header "Systems using PAM" when you copied that information about the "realtime" group.
The article does not apply to Slackware.
Studioware does things differently to achieve realtime performance. The most important are:
Append the "threadirqs" option to the kernel commandline (that is, add it to the "append" line in (e)lilo.conf or grub.conf)
Create a file called "/etc/initscript" and make it executable, and give it the following content:
Code:
# Set umask to safe level:
umask 022
# Disable core dumps:
ulimit -c 0
# Allow unlimited size to be locked into memory:
ulimit -l unlimited
# Address issue of jackd failing to start with realtime scheduling:
ulimit -r 65
# Execute the program.
eval exec "$4"
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.