Job manifests for schinit, SchOS process 1.

Every *.job file in this directory is loaded at boot. Format is sectioned
key = value; # starts a comment, keys are case-insensitive.

  Label             a reverse-DNS name, as launchd uses. Identity, not a path.
  Program           the binary to execute
  Args              argv, space separated. argv[0] is conventionally the
                    basename, so `Args = sh` for `/bin/sh`.
  RunAtLoad         start it when schinit loads
  KeepAlive         restart it when it exits
  Disabled          load it but do not start it
  ThrottleInterval  seconds between respawns (default 1)
  StandardIn        \
  StandardOut        > paths to open as fd 0, 1, 2
  StandardError     /

  [Socket <name>]
  Path              a unix socket schinit will hold on the job's behalf and
                    start the job on first connect

A KeepAlive job that exits with status 78 (sysexits.h's EX_CONFIG) is not
restarted, and schinit says which job stopped and that it stopped on purpose.
This is for a program that has looked at the machine and found nothing here it
can run against -- a driver whose device is absent, say -- which would otherwise
report the same thing every ThrottleInterval for the rest of the uptime. A job
that was killed or crashed carries a signal in its status, never matches, and
comes back exactly as KeepAlive promises.

Socket sections are parsed but not yet acted on -- that is milestone 2, and
demand launching is the whole reason this is shaped after launchd rather than
sysvinit. The key exists now so manifests do not have to change later.

Unknown keys and unknown sections are ignored rather than fatal: a manifest
written for a newer schinit must not stop this one booting the machine.