From 4c43e7e86193fe27eeb72c99428679933fd33583 Mon Sep 17 00:00:00 2001 From: Jim Garlick Date: Tue, 7 Jan 2025 15:02:36 -0800 Subject: [PATCH] doc: update flux_reactor_create(3) flags Problem: FLUX_REACTOR_SIGCHLD has been dropped from the public API but it is still mentioned in the man page. Drop it from the man page. --- doc/man3/flux_reactor_create.rst | 10 ++-------- 1 file changed, 2 insertions(+), 8 deletions(-) diff --git a/doc/man3/flux_reactor_create.rst b/doc/man3/flux_reactor_create.rst index 84b3d82fa57f..24aae6a85ad4 100644 --- a/doc/man3/flux_reactor_create.rst +++ b/doc/man3/flux_reactor_create.rst @@ -27,14 +27,8 @@ DESCRIPTION =========== :func:`flux_reactor_create` creates a :type:`flux_reactor_t` object which can -be used to monitor for events on file descriptors, ZeroMQ sockets, timers, and -:type:`flux_t` broker handles. - -There is currently only one possible flag for reactor creation: - -FLUX_REACTOR_SIGCHLD - The reactor will internally register a SIGCHLD handler and be capable - of handling flux child watchers (see :man3:`flux_child_watcher_create`). +be used to monitor for events on file descriptors, timers, and +:type:`flux_t` broker handles. :var:`flags` should be set to zero. For each event source and type that is to be monitored, a :type:`flux_watcher_t` object is created using a type-specific create function, and started