Re: issue blocking input_handler

2023-02-04 Thread James Browning via devel
> On 02/03/2023 11:35 PM PST Hal Murray wrote: > > James Browning said: > >> How about fixing the bug at ithe source rather than patching around it? > > I tried and failed then I came up with that. > > Did you get O_NONBLOCK turned on? > Something like this: > err = fcntl(sockfd, F_SETF

Re: issue blocking input_handler

2023-02-03 Thread Hal Murray via devel
James Browning said: >> How about fixing the bug at ithe source rather than patching around it? > I tried and failed then I came up with that. Did you get O_NONBLOCK turned on? Something like this: err = fcntl(sockfd, F_SETFL, O_NONBLOCK); -- These are my opinions. I hate spam. _

Re: issue blocking input_handler

2023-02-03 Thread James Browning via devel
> On 02/03/2023 2:51 PM PST Hal Murray wrote: > > James Browning said: > > I found a problem with input_handler(). If a reference clock passes a > > blocking file descriptor, input_handler can block forever. > > Who did that? Which driver? I ran across it working on a chrony socket refclock.

Re: issue blocking input_handler

2023-02-03 Thread Hal Murray via devel
James Browning said: > I found a problem with input_handler(). If a reference clock passes a > blocking file descriptor, input_handler can block forever. Who did that? Which driver? How about fixing the bug at ithe source rather than patching around it? -- These are my opinions. I hate sp