flua: fbsd: allow stdout to be captured for exec() processes

This allows us to do things like:

```
local fp = assert(fbsd.exec({"ls", "-l"}, true))
local fpout = assert(fp:stdout())

while true do

flua: fbsd: allow stdout to be captured for exec() processes

This allows us to do things like:

```
local fp = assert(fbsd.exec({"ls", "-l"}, true))
local fpout = assert(fp:stdout())

while true do
local line = fpout:read("l")
if not line then break end
print("Read: " .. line)
end

fp:close()
```

The makeman lua rewrite will use it to capture `make showconfig` output
for processing.

Reviewed by: bapt
Differential Revision: https://reviews.freebsd.org/D50539

show more ...

flua: fbsd: return a process handle to operate on when we exec()

This gives us some way to be able to write to stdin if we want to, or
as a future improvement, will allow us to extract stdout from t

flua: fbsd: return a process handle to operate on when we exec()

This gives us some way to be able to write to stdin if we want to, or
as a future improvement, will allow us to extract stdout from the
process. The handle is setup to close and waitpid() on close/gc so that
existing users wouldn't necessarily leak for the lifetime of the script
if they weren't adopted to the new model.

Reviewed by: bapt
Differential Revision: https://reviews.freebsd.org/D50538

show more ...

flua: fbsd: avoid leaking stdin pipes on error

Additionally, there's no way to get to the end without a valid
stdin_pipe[1] at the moment, so don't check for it. stdin_pipe[0] is
closed earlier, as

flua: fbsd: avoid leaking stdin pipes on error

Additionally, there's no way to get to the end without a valid
stdin_pipe[1] at the moment, so don't check for it. stdin_pipe[0] is
closed earlier, as the parent shouldn't need the read-side of the pipe.

While we're here, also free the file actions earlier and on error --
they're not necessary once posix_spawnp() has returned.

Reviewed by: bapt
Differential Revision: https://reviews.freebsd.org/D50537

show more ...

lposix: Clean up the posix namespace definitions

The posix module is subdivided according to C headers; for instance,
posix.unistd contains routines available from unistd.h, such as
chown(2).

A qui

lposix: Clean up the posix namespace definitions

The posix module is subdivided according to C headers; for instance,
posix.unistd contains routines available from unistd.h, such as
chown(2).

A quirk of our implementation is that each of the modules is a direct
entry in the global table. That is, there is no "posix" table.
Instead, "posix.foo" and "posix.bar.baz" are both top-level tables.
This is surprising and goes against Lua's shorthand of using "." to
access keys in a table. lua-posix also doesn't work this way.

Rework things so that "posix" and "posix.sys" are proper tables.
Existing flua code which uses require() to bind posix submodules to a
name will be unaffected. Code which accesses them directly using
something like _G["posix.sys.utsname"].uname() will be broken, but I
don't think anything like that exists. In particular, it is now
possible to call posix.sys.utsname.uname() without any require
statements.

Reviewed by: imp, bapt
MFC after: 2 weeks
Differential Revision: https://reviews.freebsd.org/D51158

show more ...

lposix: Use reentrant passwd and group lookup functions

The implementation of chown() in the posix module handles user and group
names as well as numeric IDs. When resolving names, be sure to use
r

lposix: Use reentrant passwd and group lookup functions

The implementation of chown() in the posix module handles user and group
names as well as numeric IDs. When resolving names, be sure to use
reentrant lookup functions rather than assuming it's safe to clobber the
internal buffers used by getpwnam() and getgrnam().

Fix some style nits while here.

Reviewed by: imp, bapt
MFC after: 2 weeks
Differential Revision: https://reviews.freebsd.org/D46555

show more ...

lyaml: vendor import lua bindings for libyaml