> -.An \&Ed Shouten Aq Mt e...@freebsd.org
> +.An \&Ed Schouten Aq Mt e...@freebsd.org
Committed. Thanks
On Mon, 26 Jun 2023 17:24:38 +0200, Paul de Weerd wrote:
> Having never heard of posix_spawn(3), I read the full manpage and
> (besides wondering "what's the point"), found that it's misspelled Ed
> Schouten's name:
Yes, that should be fixed.
- todd
Having never heard of posix_spawn(3), I read the full manpage and
(besides wondering "what's the point"), found that it's misspelled Ed
Schouten's name:
Index: posix_spawn.3
===
RCS file: /cvs/src/lib/libc/gen/posix_spawn.3,v
retrievi
On 2023-06-26, Marc Espie wrote:
> Note that a NULL environment is undefined behavior according to POSIX.
> If you read the OpenGroup description, it very clearly states that
> envp is a pointer to a NULL terminated array.
>
> Does GNU/Linux at least document that passing a NULL pointer means no
>
On Sun, Jun 25, 2023 at 07:07:33PM -0300, Lucas de Sena wrote:
> The manual already describes how posix_spawn(3) behaves when passing it
> a NULL envp, but does not make it clear that it is an OpenBSD extension:
>
> > If envp is NULL, the environment is passed unchanged from the parent
> > process
On Sun, Jun 25, 2023 at 07:07:33PM -0300, Lucas de Sena wrote:
> The manual already describes how posix_spawn(3) behaves when passing it
> a NULL envp, but does not make it clear that it is an OpenBSD extension:
>
> > If envp is NULL, the environment is passed unchanged from the parent
> > process
The manual already describes how posix_spawn(3) behaves when passing it
a NULL envp, but does not make it clear that it is an OpenBSD extension:
> If envp is NULL, the environment is passed unchanged from the parent
> process.
That differs from GNU/Linux, for example, where a NULL envp gives the
