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

To: Jason Thorpe <thorpej%me.com@localhost>
Subject: Re: Proposal to automatically make the owner/user of an accepted socket the current process
From: Emmanuel Nyarko <emmankoko519%gmail.com@localhost>
Date: Fri, 6 Jun 2025 03:00:03 +0000

On 6 Jun 2025, at 2:57 AM, Jason Thorpe <thorpej%me.com@localhost> wrote:

On Jun 5, 2025, at 7:51 PM, Emmanuel Nyarko <emmankoko519%gmail.com@localhost> wrote:

And also, fchown, no support for it yet ?

fchown()? It changes the uid/gid of a file on disk, like chown() but takes a file descriptor rather than a path.

Used it ? It exits/fails on EINVAL.

-- thorpej

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

References:
- Re: Proposal to automatically make the owner/user of an accepted socket the current process
  - From: Jason Thorpe
- Re: Proposal to automatically make the owner/user of an accepted socket the current process
  - From: Emmanuel Nyarko
- Re: Proposal to automatically make the owner/user of an accepted socket the current process
  - From: Emmanuel Nyarko
- Re: Proposal to automatically make the owner/user of an accepted socket the current process
  - From: Jason Thorpe

Prev by Date: Proposal to automatically make the owner/user of an accepted socket the current process
Next by Date: Re: Proposal to automatically make the owner/user of an accepted socket the current process
Previous by Thread: Re: Proposal to automatically make the owner/user of an accepted socket the current process
Next by Thread: Re: Proposal to automatically make the owner/user of an accepted socket the current process
Indexes:

Home | Main Index | Thread Index | Old Index