Try it, and let me know if you are able to make it work. I was not. DRC
On 7/1/20 7:19 AM, Jason Edgecombe wrote: > Hmmm, that is a problem. My only other idea is a custom udev rule. > --------------------------------------------------------------------------- > Jason Edgecombe | Linux Administrator > UNC Charlotte | The William States Lee College of Engineering > 9201 University City Blvd. | Charlotte, NC 28223-0001 > Phone: 704-687-1943 <tel:704-687-1943> > [email protected] <mailto:[email protected]> | http://engr.uncc.edu | > Facebook > --------------------------------------------------------------------------- > If you are not the intended recipient of this transmission or a person > responsible for delivering it to the intended recipient, any > disclosure, copying, distribution, or other use of any of the > information in this transmission is strictly prohibited. If you have > received this transmission in error, please notify me immediately by > reply e-mail or by telephone at > 704-687-1943 <tel:704-687-1943>. Thank you. > > > On Tue, Jun 30, 2020 at 5:19 PM DRC <[email protected] > <mailto:[email protected]>> wrote: > > The problem is that the device permissions are ultimately > controlled by the kernel module. That means that they'll be reset > whenever the module is loaded or unloaded, which can happen > whenever the 3D X server starts or someone logs in/out locally. > I'm not sure if there is a way to reliably override that. The > only reasonable approach seems to be to grant system-wide > permission to the devices while restricting the 3D X server to > vglusers only. That's a pretty common way of configuring > VirtualGL, actually. > > On 6/29/20 7:41 AM, Jason Edgecombe wrote: >> Hello, >> >> Can you set the device permissions after boot in a systemd >> service, a startup script, or an @boot cron job and have it work? >> >> Sincerely, >> Jason >> >> --------------------------------------------------------------------------- >> Jason Edgecombe | Linux Administrator >> UNC Charlotte | The William States Lee College of Engineering >> 9201 University City Blvd. | Charlotte, NC 28223-0001 >> Phone: 704-687-1943 <tel:704-687-1943> >> [email protected] <mailto:[email protected]> | >> http://engr.uncc.edu | Facebook >> >> --------------------------------------------------------------------------- >> If you are not the intended recipient of this transmission or a >> person responsible for delivering it to the intended recipient, >> any disclosure, copying, distribution, or other use of any of the >> information in this transmission is strictly prohibited. If you >> have received this transmission in error, please notify me >> immediately by reply e-mail or by telephone at >> 704-687-1943 <tel:704-687-1943>. Thank you. >> >> >> On Fri, Jun 26, 2020 at 12:11 PM DRC <[email protected] >> <mailto:[email protected]>> wrote: >> >> Sorry for the delay. I looked into this, and unfortunately, >> I don't see >> a way to accomplish what you want to accomplish. It is >> possible for >> vglserver_config to be more selective about DRI devices, but >> with nVidia >> devices, the permissions are assigned based on rules that >> VirtualGL >> specifies in /etc/modprobe.d/virtualgl.conf, using >> nVidia-specific >> driver directives. Those driver directives don't appear to allow >> permissions to be set per-device. >> >> On 12/9/19 7:02 AM, trumee wrote: >> > Sorry, I wasn't clear before. I have two devices and thus >> have /dev/nvidia0 and /dev/nvidia1. I want vglserver_config >> to put /dev/nvidia0 in vglserver group but leave /dev/nvidia1 >> alone. >> > >> >> -- >> You received this message because you are subscribed to the >> Google Groups "VirtualGL User Discussion/Support" group. >> To unsubscribe from this group and stop receiving emails from >> it, send an email to >> [email protected] >> <mailto:virtualgl-users%[email protected]>. >> To view this discussion on the web visit >> >> https://groups.google.com/d/msgid/virtualgl-users/ed4f6846-665a-ffb8-56d2-da8c753b0208%40virtualgl.org. >> >> -- >> You received this message because you are subscribed to the >> Google Groups "VirtualGL User Discussion/Support" group. >> To unsubscribe from this group and stop receiving emails from it, >> send an email to [email protected] >> <mailto:[email protected]>. >> To view this discussion on the web visit >> >> https://groups.google.com/d/msgid/virtualgl-users/CAAR6MGCbFwUeSmX%3D%2BKPC0jCrH368qJPTMMhGtz9FajchJ%2BcGmg%40mail.gmail.com >> >> <https://groups.google.com/d/msgid/virtualgl-users/CAAR6MGCbFwUeSmX%3D%2BKPC0jCrH368qJPTMMhGtz9FajchJ%2BcGmg%40mail.gmail.com?utm_medium=email&utm_source=footer>. > -- > You received this message because you are subscribed to the Google > Groups "VirtualGL User Discussion/Support" group. > To unsubscribe from this group and stop receiving emails from it, > send an email to [email protected] > <mailto:[email protected]>. > To view this discussion on the web visit > > https://groups.google.com/d/msgid/virtualgl-users/d34c63f0-e054-d897-ee4b-cde2be01a3a6%40virtualgl.org > > <https://groups.google.com/d/msgid/virtualgl-users/d34c63f0-e054-d897-ee4b-cde2be01a3a6%40virtualgl.org?utm_medium=email&utm_source=footer>. > > -- > You received this message because you are subscribed to the Google > Groups "VirtualGL User Discussion/Support" group. > To unsubscribe from this group and stop receiving emails from it, send > an email to [email protected] > <mailto:[email protected]>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/virtualgl-users/CAAR6MGDDmrmLaMSM14Rz8TCWZ8WSh-3GLv%3DUAmR1vrcJMxt%3DwA%40mail.gmail.com > <https://groups.google.com/d/msgid/virtualgl-users/CAAR6MGDDmrmLaMSM14Rz8TCWZ8WSh-3GLv%3DUAmR1vrcJMxt%3DwA%40mail.gmail.com?utm_medium=email&utm_source=footer>. -- You received this message because you are subscribed to the Google Groups "VirtualGL User Discussion/Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/virtualgl-users/dc7903f5-37ce-9035-2a2a-4447ed886b2b%40virtualgl.org.
