Hi,
I have discovered that the libusb process's file mask affects how
libusb_attach_kernel_driver() restores the driver. In my particular case, I
am dealing with usblp, so the kernel enumerates /dev/usb/lpX device files.
The /dev/usb folder is created and destroyed as necessary for the devices.
When there is a single usblp device, the libusb_detach_kernel_driver() will
cause the folder to be removed. Upon reattaching the kernel driver, the
folder is restored, and the permissions are dictated by the process's file
mask. To clarify, the individual device files are not affected by the
umask; those permissions follow the udev rules. The permissions of the
folder containing the device files are affected.
I was very surprised to see this behavior. I don't necessarily want my
application to set its own umask to deal with this issue.
Does anyone have suggestions?
Thanks,
Chris
------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
libusbx-devel mailing list
libusbx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libusbx-devel
