Page MenuHomeFreeBSD

system(3): Fix null case
ClosedPublic

Authored by des on Feb 24 2026, 1:44 PM.
Tags
None
Referenced Files
Unknown Object (File)
Sat, Apr 11, 11:46 PM
Unknown Object (File)
Sat, Apr 11, 12:26 AM
Unknown Object (File)
Wed, Apr 8, 9:51 AM
Unknown Object (File)
Sun, Apr 5, 1:10 PM
Unknown Object (File)
Mar 22 2026, 5:03 AM
Unknown Object (File)
Mar 21 2026, 8:46 AM
Unknown Object (File)
Mar 18 2026, 3:56 AM
Unknown Object (File)
Mar 17 2026, 12:54 PM
Subscribers

Details

Summary

Our manual page states that if given a null pointer, system() returns
non-zero if the shell is available and zero if it is not. This is
consistent with the C standard's description of system(), but it is not
what we actually do. What we actually do is always return non-zero, as
required by POSIX.

As the POSIX rationale explains, implementing the logic required by the
C standard does not violate POSIX, since a conforming system always has
a shell, therefore the logic will always return non-zero.

Since our libc is commonly used in non-conforming situations such as
chroots or thin jails, we should implement the full logic required by
the C standard.

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable