Arch Linux

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#40698 - [nvidia-utils] Missing documentation and some binaries

Attached to Project: Arch Linux
Opened by (Det) - Thursday, 05 June 2014, 02:26 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Tuesday, 24 June 2014, 21:40 GMT
Task Type Feature Request
Category Packages: Extra
Status Closed
Assigned To Ionut Biru (wonder)
Sven-Hendrik Haase (Svenstaro)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No


I thought I had all of these in  FS#38604 , but the following are still missing:

- /usr/bin/nvidia-cuda-mps-control
→ The control daemon for nvidia-cuda-mps-server. We currently only install the manpage.
→ See #4.1.1. in:

- /usr/bin/nvidia-persistenced
- /usr/share/man/man1/nvidia-persistenced.1.gz
- /usr/lib/systemd/system/nvidia-persistenced.service (found in nvidia-persistenced-init.tar.bz2, the creates a separate group 'nvidia-persistenced' by default)
→ When enabled, the driver is prevented from releasing device state when the device is not in use. This can improve the startup time of new clients.
→ Also used to work around some bugs where the kernel reports the GPU falling off the bus.
→ See:,

- /usr/share/man/man1/nvidia-modprobe.1.gz
→ Not essential, but a manpage for the nvidia-modprobe wouldn't hurt.

- /usr/share/doc/nvidia/html/*
→ Valuable documentation from: Only takes up about 716 KB.

Examples attached.
This task depends upon

Closed by  Sven-Hendrik Haase (Svenstaro)
Tuesday, 24 June 2014, 21:40 GMT
Reason for closing:  Implemented
Additional comments about closing:  I should have gotten them all in. Please have a look and if I missed anything open a new report.
Comment by Sven-Hendrik Haase (Svenstaro) - Monday, 09 June 2014, 00:17 GMT
Thanks for the patch. Looks good for the most part. However, why add a user when you actually mean a group?
Comment by (Det) - Monday, 09 June 2014, 05:23 GMT
Useradd is also used to make groups own the running processes. These are assigned /sbin/nologin (or /usr/bin/nologin) as their login shells in /etc/passwd to distinguish them from real interactive users.

# useradd -c 'NVIDIA Persistence Daemon' -d '/' -s /sbin/nologin -r nvidia-persistenced

is a synonym for:

# groupadd -r nvidia-persistenced
# useradd -c 'NVIDIA Persistence Daemon' -g nvidia-persistenced -d '/' -s /sbin/nologin -r nvidia-persistenced

However, taken from the non-interactive users's UIDs/GIDs are distinguished by starting from 1 and going forward, when by default (for real users) they start from 1000 to go down. Useradd alone can't set a custom group ID, so this supposedly means you'd need some assistance from the other Arch devs for choosing a proper ID, and then it can be created/removed as per the new attachment (the second one).