search for: l762

...dcmd()` (where CLI child processes talk to a daemonized copy which tracks the timers for events), around here: https://github.com/networkupstools/nut/blob/v2.8.0/clients/upssched.c#L583-L626 for the daemon and here for the child: https://github.com/networkupstools/nut/blob/v2.8.0/clients/upssched.c#L762-L787 In both cases we run an infinite loop with `select()` to wait up to 1 second and `read()` from the pipe. The common expectation is that if there is nothing to read, the program blocks in `select()` waiting for a reply from the kernel, and only returns after the specified timeout - to the poin...

...dcmd()` (where CLI child processes talk to a daemonized copy which tracks the timers for events), around here: https://github.com/networkupstools/nut/blob/v2.8.0/clients/upssched.c#L583-L626 for the daemon and here for the child: https://github.com/networkupstools/nut/blob/v2.8.0/clients/upssched.c#L762-L787 In both cases we run an infinite loop with `select()` to wait up to 1 second and `read()` from the pipe. The common expectation is that if there is nothing to read, the program blocks in `select()` waiting for a reply from the kernel, and only returns after the specified timeout - to the poin...

...hild processes talk to a daemonized copy > which tracks the timers for events), around here: > https://github.com/networkupstools/nut/blob/v2.8.0/clients/upssched.c#L583-L626 > for the daemon and here for the child: > https://github.com/networkupstools/nut/blob/v2.8.0/clients/upssched.c#L762-L787 > > In both cases we run an infinite loop with `select()` to wait up to 1 > second and `read()` from the pipe. The common expectation is that if there > is nothing to read, the program blocks in `select()` waiting for a reply > from the kernel, and only returns after the specifi...

...hild processes talk to a daemonized copy > which tracks the timers for events), around here: > https://github.com/networkupstools/nut/blob/v2.8.0/clients/upssched.c#L583-L626 > for the daemon and here for the child: > https://github.com/networkupstools/nut/blob/v2.8.0/clients/upssched.c#L762-L787 > > In both cases we run an infinite loop with `select()` to wait up to 1 > second and `read()` from the pipe. The common expectation is that if there > is nothing to read, the program blocks in `select()` waiting for a reply > from the kernel, and only returns after the specifi...

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,