Re: Strangeness in 842 Fix

2025-04-14 Thread Matt Selsky via devel
On Mon, Apr 14, 2025 at 03:16:46PM -0700, Fred Wright via devel wrote: > > I was just looking at recent changes, and came across commit 4756b6317. I > don't know anything specifically about the *_TIMESTAMPNS_OLD stuff, but I do > know that the SO_* symbols are for the socket options and the SCM_*

Re: Strangeness in 842 Fix

2025-04-14 Thread Hal Murray via devel
> I do know that the SO_* symbols are for the socket options and the SCM_* > symbols are for the CMSG types, so I don't see how this could possibly be > correct. Note the code immediately above it. The OLD stuff is a mess. I did it the way you expect, but that didn't work because SCM_TIMESTA

Re: Strangeness in 842 Fix

2025-04-14 Thread James Browning via devel
On Monday, April 14, 2025 3:16:46 PM Pacific Daylight Time Fred Wright via devel wrote: > I was just looking at recent changes, and came across commit 4756b6317. > I don't know anything specifically about the *_TIMESTAMPNS_OLD stuff, but > I do know that the SO_* symbols are for the socket options

Strangeness in 842 Fix

2025-04-14 Thread Fred Wright via devel
I was just looking at recent changes, and came across commit 4756b6317. I don't know anything specifically about the *_TIMESTAMPNS_OLD stuff, but I do know that the SO_* symbols are for the socket options and the SCM_* symbols are for the CMSG types, so I don't see how this could possibly be

Re: Strangeness in 842 Fix

2025-04-14 Thread Fred Wright via devel
On Mon, 14 Apr 2025, Hal Murray wrote: I do know that the SO_* symbols are for the socket options and the SCM_* symbols are for the CMSG types, so I don't see how this could possibly be correct. Note the code immediately above it. The OLD stuff is a mess. I did it the way you expect, but