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

To: tech-kern%NetBSD.org@localhost
Subject: Re: Proposal to automatically make the owner/user of an accepted socket the current process
From: Mouse <mouse%Rodents-Montreal.ORG@localhost>
Date: Sun, 8 Jun 2025 07:21:19 -0400 (EDT)

> So after a short reading, discovered Unix Domain Sockets also use
> file descriptors for data exchange(communication).

All sockets do - well, almost all; it is possible for a socket to exist
without any process having a file descriptor referring to it, but it's
rare.  (The only examples I know of are sockets in transit in
SCM_RIGHTS messages, when the sender has closed its descriptor and the
receiver hasn't received it yet, and a few kernel-internal uses such as
the NFS client.)

/~\ The ASCII				  Mouse
\ / Ribbon Campaign
 X  Against HTML		mouse%rodents-montreal.org@localhost
/ \ Email!	     7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B

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
- Re: Proposal to automatically make the owner/user of an accepted socket the current process
  - From: Emmanuel Nyarko

Prev by Date: Working on Discard for FFS
Next by Date: Retrieving MAC address from struct ifnet
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