It is complaining about not being able to find the bitcoin-cli binary of the Bitcoin Core installation (which is normal since you are running it from a location that is not on the $PATH hence it can't find it).
To fix this issue you can tell lightningd explicitly which binary to use as bitcoin-cli by doing this:
Unless you want to test multiple versions of the lightningd binary, there is no need to check the source code out multiple times, since the binaries can be shared among multiple instances.
Assuming you are in the root directory of the source code, and you've executed ./configure and make, you can start multiple instances like this:
$ lightningd/lightningd -...
you can run lightningd --help and get a list of arguments you can use to start lightning from the output there ist:
--lightning-dir=<dir> Set working directory. All other files are
relative to this
this means that you can set ...
I wrote the fundchannel_start/fundchannel_complete pathway. You should not broadcast the signed funding transaction until after you have successfully called fundchannel_complete for each of the peers. This is because fundchannel_complete secures the commitment transactions that are necessary to spend the funding transaction output for that channel. By ...
Yes, there are basically two ways to avoid becoming a forwarding node:
Do not announce your channels, and keep them private
Reject any incoming HTLC that is not destined for you
The first is supported by the protocol itself, and is a proactive measure against forwarding any payment that is not destined for you, while the latter is a reactive measure and ...
The TL;DR answer is: Yes it is totally possible, but as far as I know not implemented in any lightning node software at this time.
However I wish to elaborate a little bit. In your question you wrote:
The reasons could be that forwarding a payment will require it to forward the htlc, fulfill it as well as compute the onion for routing to the next node ...
I've written a plug-in for c-lightning that emulates lncli feereport command of LND. For full functionality, including day_fee_sum, week_fee_sum and month_fee_sum calculations, requires c-lightning v0.7.1 or newer (older versions didn't save timestamps for historical forwards).