5 Commits

Author	SHA1	Message	Date
darosior	d37a2d7c3e	doc/manpages: regenerate manpages using markdown templates	2019-08-22 01:35:01 +00:00
Rusty Russell	83e654a106	close: change to a unilateraltimeout argument. ... `close` takes two optional arguments: `force` and `timeout`. `timeout` doesn't timeout the close (there's no way to do that), just the JSON call. `force` (default `false`) if set, means we unilaterally close at the timeout, instead of just failing. Timing out JSON calls is generally deprecated: that's the job of the client. And the semantics of this are confusing, even to me! A better API is a timeout which, if non-zero, is the time at which we give up and unilaterally close. The transition code is awkward, but we'll manage for the three releases until we can remove it. The new defaults are to unilaterally close after 48 hours. Fixes: #2791 Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>	2019-08-09 05:47:16 +00:00
ZmnSCPxj	e588737511	peer_control: Have close accept channel IDs also.	2018-05-03 22:47:07 +02:00
Felix	52c243852e	documentation: s/Protocol/Command/	2018-04-27 14:00:16 +02:00
ZmnSCPxj	2cee1ab20f	peer_control: Make close wait for complete closure, with timeout. ... Also report tx and txid, and whether we closed unilaterally or bilaterally, if we could close the channel. Also make a manpage. Fixes: #1207 Fixes: #714 Fixes: #622	2018-04-23 05:24:46 +00:00