--- Log opened Fri Feb 15 00:00:50 2019 02:16 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...] 02:22 -!- spinza [~spin@155.93.246.187] has joined #c-lightning 03:28 -!- rh0nj [~rh0nj@88.99.167.175] has quit [Remote host closed the connection] 03:29 -!- rh0nj [~rh0nj@88.99.167.175] has joined #c-lightning 06:28 -!- BillyGarrison [2f377bca@gateway/web/freenode/ip.47.55.123.202] has joined #c-lightning 06:28 < BillyGarrison> Hi all, 06:29 < BillyGarrison> If I have general questions about c-lightning is the c-lightning mailing list an okay spot for them? Or is that reserved for more formal business? 06:30 < BillyGarrison> For example, I'm wondering where private keys are stored and if/how/where the Bitcoin script is stored for transactions (based on my understanding that you must store a private key as well as the unlocking script since the blockchain only stores the script hash?) 06:30 < BillyGarrison> And if the mailing list is not a good spot for such questions, what is the best place? 06:30 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...] 06:37 < molz> there's a "c-lightning mailing list"? 06:45 < BillyGarrison> c-lightning@lists.ozlabs.org is listed in the c-lightning GitHub readme 06:48 < molz> ah 06:52 -!- spinza [~spin@155.93.246.187] has joined #c-lightning 06:53 < molz> BillyGarrison, i guess you can 06:54 < molz> there's not much activity on the list and someone is also asking questions on there 07:11 < t0mix> here is very ugly (not speed optimized), but working bash script to check all forwards on c-lightning node. with outputs example like this: 07:11 < t0mix> from OpenNode 07:11 < t0mix> to WRONGSPAWN 07:11 < t0mix> https://pastebin.com/6Bh6LB72 07:11 < t0mix> status "settled" 07:12 < t0mix> if anybody find it interesting, it's free to use. if anybody find it stupid, please let me also know. I'm be happy to be told the truth =D 07:15 < t0mix> point was to somehow measure which connections are used.. in human readable form 07:44 -!- cubancorona [cubancoron@gateway/vpn/privateinternetaccess/cubancorona] has quit [Quit: Leaving] 09:27 < BillyGarrison> Thanks @molz. 09:28 < BillyGarrison> t0mix: That's interesting, thanks for sharing. Nice for a Linux noob like me to learn from as well 09:29 < fiatjaf> how can I know what does an exit code 1 mean? 09:29 < fiatjaf> it can be lots of different stuff, but no message is printed 09:29 < fiatjaf> (I'm using the latest master) 09:30 < fiatjaf> actually, I get no stdout, just an exit with code 1 09:31 < fiatjaf> running this command: /home/fiatjaf/lightning/lightningd/lightningd --network regtest --bitcoin-cli /home/fiatjaf/bitcoin/bin/bitcoin-cli --bitcoin-rpcport=10287 --bitcoin-datadir=/tmp/bitcoin.isaimlbq --lightning-dir /tmp/lightning-a.ot6pinfk --lightningd_bind-addr 127.0.0.1:9870 11:21 -!- rh0nj [~rh0nj@88.99.167.175] has quit [Remote host closed the connection] 11:24 -!- rh0nj [~rh0nj@88.99.167.175] has joined #c-lightning 12:18 -!- BillyGarrison [2f377bca@gateway/web/freenode/ip.47.55.123.202] has quit [Ping timeout: 256 seconds] 12:52 -!- BillyGarrison [2f377bca@gateway/web/freenode/ip.47.55.123.202] has joined #c-lightning 14:46 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...] 15:02 -!- spinza [~spin@155.93.246.187] has joined #c-lightning 15:05 -!- kexkey [~kexkey@192.230.35.136] has joined #c-lightning 16:22 -!- Amperture [~amp@24.136.5.183] has joined #c-lightning 16:22 -!- Amperture [~amp@24.136.5.183] has quit [Remote host closed the connection] 16:23 -!- Amperture [~amp@24.136.5.183] has joined #c-lightning 16:25 < m-schmoock> cdecker: what would be the correct way to let json controller peer_control.c tell a channeld to update its peer settings and do a send_channel_update? I am a bit lost at the point where I need to propagate new channel fee settings to the various daemons... 16:27 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has joined #c-lightning 16:27 < m-schmoock> I think the right way would be to trigger channeld somehow and update its peer->fee_base and peer->fee_per_satoshi value and call a send_channel_update afterwards 16:28 < m-schmoock> this way gossipd would know and listchannels would be able to just return the values from gossip 16:34 < fiatjaf> got some useful output with strace. 16:37 -!- Kostenko [~Kostenko@185.183.106.227] has quit [Remote host closed the connection] 16:39 < m-schmoock> fiatjaf: if you still have this try the following. first `git grep "exit(1)"` will show you any location where exit 1 is called. 16:39 < m-schmoock> secondly, you can place a debug break using `gdb lightnind` 16:40 < m-schmoock> just type in "break exit" and run 16:40 < m-schmoock> you should see the stack when using "bt" (backtrace) 16:40 < m-schmoock> thats how I found the error pipe closed bug last week 16:42 < m-schmoock> Are you sure you compiled the latest master correctly and are not using an old binary? the stdpipes close bug should really not happen anymore, but who knows 16:42 < m-schmoock> gn8 16:44 < fiatjaf> I'm not very familiar with this gdb thing, but I'll try it next time. 16:45 < fiatjaf> this time it was a different error, and more stupid: I was passing a wrong cli argument. 16:45 < fiatjaf> strace gave me that info. 16:45 < m-schmoock> you should really try gdb. its very easy to get the basic commands 16:46 < m-schmoock> just "break and "list to view code if required 16:46 < m-schmoock> you will be amazed how useful this can be 16:47 < m-schmoock> the art of debuggind :> 16:52 -!- BillyGarrison [2f377bca@gateway/web/freenode/ip.47.55.123.202] has quit [Quit: Page closed] 17:23 -!- Kostenko [~Kostenko@185.183.106.228] has joined #c-lightning 18:09 < fiatjaf> seems truly joyful 18:38 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...] 18:48 -!- spinza [~spin@155.93.246.187] has joined #c-lightning 19:32 -!- m-schmoock [~will@schmoock.net] has quit [Remote host closed the connection] 20:55 -!- Eagle[TM] [~EagleTM@unaffiliated/eagletm] has joined #c-lightning 20:55 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has quit [Ping timeout: 245 seconds] 21:41 -!- CubicEarth [~CubicEart@c-67-168-1-172.hsd1.wa.comcast.net] has quit [Ping timeout: 246 seconds] 21:41 -!- spinza [~spin@155.93.246.187] has quit [Ping timeout: 246 seconds] 21:46 -!- CubicEarth [~CubicEart@c-67-168-1-172.hsd1.wa.comcast.net] has joined #c-lightning 22:06 -!- kexkey [~kexkey@192.230.35.136] has quit [Ping timeout: 250 seconds] --- Log closed Sat Feb 16 00:00:51 2019