search for: conn_add

...re other `upssched` processes present, or look in `/proc/PIDNUM/fd/` of the daemonized and looping `upssched`... If anyone decides to track through the code, the potential processing loop goes checkconf -> conf_arg -> parse_at -> sendcmd -> daemon if needed -> start_daemon -> conn_add(pipefd) or sock_read(conn) with short-lived child processes (command-line launched from `upsmon`) parsing the configuration to pick the part relevant to them per envvars, and talk to the daemon (fork one if needed) to start/cancel the timers. Jim On Tue, Jun 13, 2023 at 8:33?AM Kari Lempi?inen &l...

...re other `upssched` processes present, or look in `/proc/PIDNUM/fd/` of the daemonized and looping `upssched`... If anyone decides to track through the code, the potential processing loop goes checkconf -> conf_arg -> parse_at -> sendcmd -> daemon if needed -> start_daemon -> conn_add(pipefd) or sock_read(conn) with short-lived child processes (command-line launched from `upsmon`) parsing the configuration to pick the part relevant to them per envvars, and talk to the daemon (fork one if needed) to start/cancel the timers. Jim On Tue, Jun 13, 2023 at 8:33?AM Kari Lempi?inen &l...

...present, or look in `/proc/PIDNUM/fd/` of the daemonized and looping > `upssched`... > > If anyone decides to track through the code, the potential processing loop > goes > checkconf -> conf_arg -> parse_at -> sendcmd -> daemon if needed -> > start_daemon -> conn_add(pipefd) or sock_read(conn) > with short-lived child processes (command-line launched from `upsmon`) > parsing the configuration to pick the part relevant to them per envvars, > and talk to the daemon (fork one if needed) to start/cancel the timers. > > Jim > > On Tue, Jun 13, 2...

...present, or look in `/proc/PIDNUM/fd/` of the daemonized and looping > `upssched`... > > If anyone decides to track through the code, the potential processing loop > goes > checkconf -> conf_arg -> parse_at -> sendcmd -> daemon if needed -> > start_daemon -> conn_add(pipefd) or sock_read(conn) > with short-lived child processes (command-line launched from `upsmon`) > parsing the configuration to pick the part relevant to them per envvars, > and talk to the daemon (fork one if needed) to start/cancel the timers. > > Jim > > On Tue, Jun 13, 2...

Hi, I ran the strace command while upssched was 100% CPU hungry. This is what I got: 1686633611.702798 read(7, "", 1) = 0 <0.000004> 1686633611.702816 read(7, "", 1) = 0 <0.000004> 1686633611.702834 pselect6(11, [7 10], NULL, NULL, {tv_sec=1, tv_nsec=0}, NULL) = 1 (in [7], left {tv_sec=0, tv_nsec=999998800}) <0.000006> 1686633611.702862 read(7,

Hi, I ran the strace command while upssched was 100% CPU hungry. This is what I got: 1686633611.702798 read(7, "", 1) = 0 <0.000004> 1686633611.702816 read(7, "", 1) = 0 <0.000004> 1686633611.702834 pselect6(11, [7 10], NULL, NULL, {tv_sec=1, tv_nsec=0}, NULL) = 1 (in [7], left {tv_sec=0, tv_nsec=999998800}) <0.000006> 1686633611.702862 read(7,