Better FD for the host-side portal code?

Better FD for the host-side portal code?

[Demi Marie Obenour]

[-- Attachment #1.1.1: Type: text/plain, Size: 241 bytes --]

I saw that the host-side portal code uses FD 0 for the listening socket.
Would it be better to use a different file descriptor for that?
Alternatively, I can dup() /dev/null over stdin.
-- 
Sincerely,
Demi Marie Obenour (she/her/hers)

[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 7253 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Re: Better FD for the host-side portal code?

[Alyssa Ross]

[-- Attachment #1: Type: text/plain, Size: 362 bytes --]

Demi Marie Obenour <demiobenour@gmail.com> writes:

> I saw that the host-side portal code uses FD 0 for the listening socket.
> Would it be better to use a different file descriptor for that?
> Alternatively, I can dup() /dev/null over stdin.

FD 0 is used on purpose.  This is inetd-style socket activation, a
standard interface supported by service managers.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]