> Adding a PolicyKit authorization to use RDMA devices is not practically > any harder than adding a group; in fact, maintenance-wise it's > substantially easier.
I have to admit I have no idea how to do that. But anyway, what's the point? No one is wants to change their app to talk to PolicyKit to request access to a device node just to run on Ubuntu. > HAL may then be used to apply an ACL to the devices automatically if you > want raw library aaccess. How would that work? On a system with the rdma_ucm module loaded (so /dev/infiniband/rdma_cm exists), I see nothing promising-looking in lshal to tell hal about. And what's the advantage to using hal to change group permissions on a file when udev can create it with the correct permissions? A very common use case would be a multi-user cluster, where MPI jobs spawn processes on many nodes using ssh, with possibly multiple different users processes running on a node at once. For example, Open MPI (already in the Ubuntu archive) is typically used with RDMA in this way. And MPI is hard enough to configure without trying to explain to users that they get permission denied errors because their ConsoleKit can't connect to the session bus or something like that. -- Ubuntu is missing /dev/infiniband/rdma_cm group ownership udev rule https://bugs.launchpad.net/bugs/256216 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
