Gene Heskett wrote:
Attached.
well, it was really for you to see. anyway, a file of name '*.cgi' is for
use in a web browser, and not a true command line executable. even tho it
was found by 'locate stat|grep bin/'.
my bad for not explaining it mo' betta than,
you do not run a '.cgi' from a
On Saturday 02 January 2010, g wrote:
Gene Heskett wrote:
Do we have a usb monitoring tool that can detect and name the processes
that are apparently fighting over a device plugged into a semi remote usb
hub, a 7 port Alps gizmo plugged into one of the mobo ports?
see reply to 'subject: nut 0
Gene Heskett wrote:
Thanks, I hadn't tried that exact strategy yet, duh... However, nothing that
looks applicable seems to appear.
in meantime of my reply post and getting back into f-12, i opened yumex
and ran a filter of 'monitor' to see what was there. none of which stated
specifically
On Saturday 02 January 2010, g wrote:
Gene Heskett wrote:
Thanks, I hadn't tried that exact strategy yet, duh... However, nothing
that looks applicable seems to appear.
in meantime of my reply post and getting back into f-12, i opened yumex
and ran a filter of 'monitor' to see what was there.
Greetings all;
Do we have a usb monitoring tool that can detect and name the processes that
are apparently fighting over a device plugged into a semi remote usb hub, a 7
port Alps gizmo plugged into one of the mobo ports?
Or is it possible that because it is not plugged directly into the
Gene Heskett wrote:
Do we have a usb monitoring tool that can detect and name the processes that
are apparently fighting over a device plugged into a semi remote usb hub, a 7
port Alps gizmo plugged into one of the mobo ports?
see reply to 'subject: nut 0 vs f10 winner'.
i believe that
