Greg Erskine wrote:
> With my limited knowledge of udev, I can't see a way to make a truly
> generic solution.
>
> In some of the udev.rules there is already some product specific code.
> The potential work to do USB properly is enormous!
>
> I think?? this problem only occurs if the RPi and DAC are powered
> independently.
>
> I have learnt/remembered that manually using squeezelite init.d script
> can create situations where the squeezelite process is running without
> the appropriate pid file and visa versa. This causes confusion during
> testing. I recall now why I included "force" option to brutally kill
> squeezelite.
>
> I have been doing my testing on a synced piCorePlayer. Its weird seeing
> the consequences of inserting a USB device in one piCorePlayer has on
> another piCorePlayer.
A way could be to execute my script every time an USB device Is plug-in.
Is not a problem because the script checks the status of squeezelite and
if It Is already on, nothing will happen. The solution Is to remove the
two attrib strings in udev rule (Idvendor and idproduct) and replace
them with this: ENV{DEVTYPE}=="usb_device"
In this way the script Will run everytime each USB device Is plug-in
(USB PEN drive, mouse USB, dac USB etc).
It Is less elegant but It Is "generic"
------------------------------------------------------------------------
PaoloFazari's Profile: http://forums.slimdevices.com/member.php?userid=71242
View this thread: http://forums.slimdevices.com/showthread.php?t=112996
_______________________________________________
unix mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/unix
