Contributions are welcomed.

You may wish to read the Contributors' Study Guide if you are unfamiliar with the problems of service management.

These should begin with one or more lines like this, summarising each change. Each should be ideally 50 or fewer characters in length:

subsystem: short description of changes

For most commits, two line-feed/carriage-returns should follow, then a longer-form description of the changes, limited to at most 80 characters per line. Multiple paragraphs may be used.

An example commit message:

cgrpfs: update to latest main
scheduler: read pipe before proceeding in subproc

The latest cgrpfs implements poll() on NetBSD, permitting notification of
CGroup emptiness events.

It's important to make sure the subprocess doesn't try to do anything until
we have placed it under tracking. This commit makes the subprocess wait on
a byte to be read to a pipe by the scheduler before it proceeds to set up
state and launch the service process.