Dear Experts, It seems that the signal that can be used with USBDEVFS_DISCSIGNAL and in usbdevfs_urb.signr is limited to the real-time signals SIGRTMIN to SIGRTMAX. What's the rationale for this restriction? I believe that a process can kill() itself with any signal number, can't it? I was planning to use SIGIO for usbdevfs_urb.signr and SIGTERM (uncaught) for USBDEVFS_DISCSIGNAL. I don't think I'll have a problem with using SIGRTMIN+n instead, but I'm curious to know if there's some subtle problem with the non-real-time signals that I should be aware of.
Regards, Phil. ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Linux-usb-users@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
