On Fri, Sep 23, 2022 at 05:34:26PM -0400, David H. Gutteridge wrote: > It's not just O_NONBLOCK that can be expected/desired, vte wants to set > O_CLOEXEC as well. The Linux kernel accepts and applies both of those > flags in a posix_openpt(3) call.
There should be no path through open(2) where O_CLOEXEC doesn't work! It is not a property of the underlying object. Or absolutely shouldn't be, anyway. -- David A. Holland dholl...@netbsd.org
