Re: kqueue(2) and close-on-exec

2023-08-14 Thread Visa Hankala
On Sun, Aug 13, 2023 at 05:58:01PM -0700, Philip Guenther wrote: > I think that changing the behavior of the existing API in a way that > gratuitously increases the differences between BSDs is unwise. IMHO, we > should follow NetBSD on this and add kqueue1(), that being obviously > consistent with

Re: kqueue(2) and close-on-exec

2023-08-13 Thread Philip Guenther
I think that changing the behavior of the existing API in a way that gratuitously increases the differences between BSDs is unwise. IMHO, we should follow NetBSD on this and add kqueue1(), that being obviously consistent with the previous 'add flags argument' extensions: pipe2(), dup3(), and accep

kqueue(2) and close-on-exec

2023-08-13 Thread Visa Hankala
FreeBSD and NetBSD have variants of the kqueue(2) system call that allow setting the close-on-exec flag on the returned file descriptor. In general, I think it is good that the flag can be set atomically for new descriptors. However, it seems to me that it is almost surely a mistake if a kqueue de