Yes, the exit doesn't do anything, likely a cut and paste from
development files. It was not intended to kill the daemon. (I don't
think)
Make a local copy of the init.d script and then just call that.
piCorePlayer a small player for the Raspberry Pi in RAM.
Homepage: https://www.picorepla
Greg Erskine wrote:
> You don't have wifi going but net-usb has connected to your network.
> Your IP has been set.
>
> So everything is OK :D
What's the next step with wifi? Should I be able to connect Squeezebox
now, via ethernet?
You don't have wifi going but net-usb has connected to your network.
Your IP has been set.
So everything is OK :D
Greg Erskine's Profile: http://forums.slimdevices.com/member.php?userid=7403
View this thread: http://forum
paul- wrote:
> just lower case, we assume most windows users don't know how to remove
> the .txt, so we check for that. So now you have a USB hub can you
> connect a keyboard.
>
> need to see the contents of /var/log/pcp_boot.log
Output from above command...
27351
+--
paul- wrote:
> The difference between the huge distributions and pCP is that we don't
> run large resource hogging daemons. The network managers can cycle
> through various settings when a connection fails, we cannot. In the
> majority of the cases everything works fine.Without having acce
Thank you for the suggestion, that's of course an option. I think it
would be more elegant if the pcp-bt init script supported an extra
argument "init" that would just call it's init function without actually
starting the connect daemon. That way, I could stay closer to the
original pCP. Would ad
Manul wrote:
> Next update: I managed to get my script to start and stop on
> connection/disconnection of the remote via udev rules. The only problem
> I have now is that pcp-bt-connect-daemon somehow interferes: While that
> is running the udev rule seems to spawn my script multiple times inste
