Re: Proposal to automatically make the owner/user of an accepted socket the current process

Errmmm, I was thinking that it maybe becomes a default behavior.

I mean every socket should be owned by the process that the socket was created for.

But maybe too, being a switched feature is also considered. 

> On 5 Jun 2025, at 3:17 PM, Jonathan Stone <[email protected]> wrote:
> 
> Have you considered making this an "opt-in" with a setsockopt() to enable/disable the change?
> And maybe a sysctl to set the system-wide default for processes which don't explicitly set that setsockopt()? Or does that "go without saying"?
> 
> if nothing else, that lets the adventurous experiment with the change, for specific (modified and recompiled) services, without affecting anything else.

A scoffer seeks wisdom in vain, but knowledge is easy for a man of understanding.
Emmanuel