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

To: Thor Lancelot Simon <tls%panix.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:04:01 +0000

On 5 Jun 2025, at 11:12 PM, Thor Lancelot Simon <tls%panix.com@localhost> wrote:

On Thu, Jun 05, 2025 at 04:36:43PM +0000, Emmanuel Nyarko wrote:
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.

What will happen when a socket changes hands by file descriptor passing
over a Unix domain socket?

I think Jonathan Stone pointed out a few maybe “incompatibilities” with the Unix Domain Socket. I think I would also have to do some research into that as well since I don’t have that much knowledge and experience in that domain.

Thor

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

References:
- 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: Jonathan Stone
- 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: Thor Lancelot Simon

Prev by Date: Re: 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