core-lightning/common/subdaemon.h

#ifndef LIGHTNING_COMMON_SUBDAEMON_H
#define LIGHTNING_COMMON_SUBDAEMON_H
#include "config.h"
#include <common/daemon.h>
struct htable;

/* daemon_setup, but for subdaemons */
void subdaemon_setup(int argc, char *argv[]);

/* Only defined if DEVELOPER */
bool dump_memleak(struct htable *memtable);

#endif /* LIGHTNING_COMMON_SUBDAEMON_H */
subdaemon.c: subdaemon_setup() routine for all daemons. Our handling of SIGPIPE was incoherent and inconsistent, and we had much cut & paste between the daemons. They should ALL ignore SIGPIPE, and much of the rest of the boilerplate can be shared, so should be. Reported-by: @ZmnSCPxj Fixes: #528 Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> 2018-01-08 11:01:09 +01:00			`#ifndef LIGHTNING_COMMON_SUBDAEMON_H`
			`#define LIGHTNING_COMMON_SUBDAEMON_H`
			`#include "config.h"`
common/daemon: common routines for all daemons. In particular, the main daemon and subdaemons share the backtrace code, with hooks for logging. The daemon hook inserts the io_poll override, which means we no longer need io_debug.[ch]. Though most daemons don't need it, they still link against ccan/io, so it's harmess (suggested by @ZmnSCPxj). This was tested manually to make sure we get backtraces still. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> 2018-03-29 04:06:45 +02:00			`#include <common/daemon.h>`
common: reduce header differences for DEVELOPER vs non-DEVELOPER. `make update-mocks` is usually run in DEVELOPER mode, but then it includes definitions for functions which aren't declared in non-DEVELOPER mode. We hacked this in a few places, but it's fragile, and worst, now we have EXPERIMENTAL_FEATURES as well, it's complex. Instead, declare developer-only functions (but don't define them). This is a bit more awkward if you accidentally use one in non-DEVELOPER code (link error rather than compile error), but makes autogenerating test mocks much easier. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> 2019-09-06 06:40:05 +02:00			`struct htable;`
subdaemon.c: subdaemon_setup() routine for all daemons. Our handling of SIGPIPE was incoherent and inconsistent, and we had much cut & paste between the daemons. They should ALL ignore SIGPIPE, and much of the rest of the boilerplate can be shared, so should be. Reported-by: @ZmnSCPxj Fixes: #528 Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> 2018-01-08 11:01:09 +01:00
common/daemon: common routines for all daemons. In particular, the main daemon and subdaemons share the backtrace code, with hooks for logging. The daemon hook inserts the io_poll override, which means we no longer need io_debug.[ch]. Though most daemons don't need it, they still link against ccan/io, so it's harmess (suggested by @ZmnSCPxj). This was tested manually to make sure we get backtraces still. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> 2018-03-29 04:06:45 +02:00			`/* daemon_setup, but for subdaemons */`
subdaemon.c: subdaemon_setup() routine for all daemons. Our handling of SIGPIPE was incoherent and inconsistent, and we had much cut & paste between the daemons. They should ALL ignore SIGPIPE, and much of the rest of the boilerplate can be shared, so should be. Reported-by: @ZmnSCPxj Fixes: #528 Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> 2018-01-08 11:01:09 +01:00			`void subdaemon_setup(int argc, char *argv[]);`

common: reduce header differences for DEVELOPER vs non-DEVELOPER. `make update-mocks` is usually run in DEVELOPER mode, but then it includes definitions for functions which aren't declared in non-DEVELOPER mode. We hacked this in a few places, but it's fragile, and worst, now we have EXPERIMENTAL_FEATURES as well, it's complex. Instead, declare developer-only functions (but don't define them). This is a bit more awkward if you accidentally use one in non-DEVELOPER code (link error rather than compile error), but makes autogenerating test mocks much easier. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> 2019-09-06 06:40:05 +02:00			`/* Only defined if DEVELOPER */`
common/subdaemon: helpers for dumping memleaks in subdaemons. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> 2018-11-21 22:46:37 +01:00			`bool dump_memleak(struct htable *memtable);`

subdaemon.c: subdaemon_setup() routine for all daemons. Our handling of SIGPIPE was incoherent and inconsistent, and we had much cut & paste between the daemons. They should ALL ignore SIGPIPE, and much of the rest of the boilerplate can be shared, so should be. Reported-by: @ZmnSCPxj Fixes: #528 Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> 2018-01-08 11:01:09 +01:00			`#endif /* LIGHTNING_COMMON_SUBDAEMON_H */`