sbase/getconf.1
Michael Forney c225d88d49 getconf: Report invalid variables as errors
Printing `undefined` to stdout means that the variable is valid but not
set. Instead, report an error in this case.

linux 4.13 appends the result of `getconf LFS_CFLAGS` to HOSTCFLAGS,
even if it prints `undefined`. This is arguably a bug in the Makefile,
but even so, getconf shouldn't report that unsupported variables are
valid.
2017-09-03 17:23:28 -07:00

61 lines
844 B
Groff

.Dd 2015-10-08
.Dt GETCONF 1
.Os sbase
.Sh NAME
.Nm getconf
.Nd get configuration values
.Sh SYNOPSIS
.Nm
.Op Fl v Ar spec
.Ar var
.Ar [path]
.Sh DESCRIPTION
.Nm
writes the value of the variable
.Ar var
to stdout.
.sp
If
.Ar path
is given,
.Ar var
is matched against configuration values from
.Xr pathconf 3 .
If
.Ar path
is not given,
.Ar var
is matched against configuration values from
.Xr sysconf 3 ,
.Xr confstr 3
and limits.h (Minimum and Maximum).
.sp
If
.Ar var
is not defined,
.Nm
writes "undefined" to stdout.
.Sh OPTIONS
.Bl -tag -width Ds
.It Fl v Ar spec
Ignored.
.El
.Sh EXIT STATUS
.Bl -tag -width Ds
.It 0
.Ar var
was matched and its value written successfully.
.It 1
An error occured or
.Ar var
was invalid.
.El
.Sh STANDARDS
The
.Nm
utility is compliant with the
.St -p1003.1-2013
specification except from the
.Op Fl v
flag.