Bitcraze Forums

I did not parametrized cfheadless with debugfile, I am doing to do and have a look at syslog...

Looking at syslog file, you can see you are right, the problem is udev timeout. But I don't know how to avoid this, I tested udevadm --timeout ... but this command does not exist here. Is it possible that some answer to the RUN command in 99-...rules is not implemented?
Here are the files:
syslog: and nohup.out file:

Hum, I think I got an idea that could work: what about creating a "systemd unit" for the headless client? This can be started (or not) at startup. Then the udev rules will just contain: "systemclt restart cfheadless". This way the headless client is lauched and handled directly with systemd so there should not be any timeout.

Hi
I tested the method, looks correct. Easy to install systemd unit in /etc/systemd/system. No more time out.
But I do not yet succeed in launching unit using udev rule. Nexot step...

Hi *
The answer is here:
https://lists.freedesktop.org/archives/ ... 07391.html
I will delve into the question.... and open a new post if I find a solution.
Perhaps an issue should be emitted?
BR *
Jean-Claude

Thanks for the update! If you find how to update the file to make it work, an issue (or a pull request) would be great .

OK

HI
I finally got a solution. The problem comes from the new booting process of Linux called "systemd". Launching the client when connecting the Crazyradio to the Raspberry needs to define a "service" as required in systemd process.
See an issue in Bitcraze's github repository bitcraze-raspberry-pi. Perhaps wiki should be added the question but my english is too frenchy....
BR
Jean-Claude