NAME

appjail-startup — Unattended command to start jails and other related things

SYNOPSIS

DESCRIPTION

The appjail startup utility starts jails, performs NAT per network, and starts healthcheckers at startup without user intervention. This is the core of RC scripts.

Unlike jails and network NAT, starting healthcheckers is a long-term operation, so only the start command is implemented. Remember that healthcheckers can be stopped using the RC script or when all healthcheckers are stopped, i.e. they fail.

jails only starts jails that have the boot flag set. This command organizes the list of jails using a priority that is set individually for each jail: jails with a lower number ⟨starting from 0⟩ are started first. If the USE_PARALLEL parameter is enabled, jails are started in parallel depending on their priority, e.g. if we have jails A ⟨0⟩, B ⟨0⟩, C ⟨1⟩ and D ⟨2⟩, jails A and B are started first ⟨in parallel⟩, then C is started and then D is started.

nat networks performs NAT per network at startup. If the USE_PARALLEL_NATNET parameter is enabled, this operation is performed in parallel.

EXIT STATUS

The appjail startup utility exits 0 on success, and >0 if an error occurs. It may fail for one of the following reasons:

• EX_DATAERR: The log name specified in the STARTUPLOG_NAME parameter is invalid.

SEE ALSO

appjail-jail(1) appjail-rstop(1) appjail-start(1) appjail-stop(1) sysexits(3)

AUTHORS

Jesús Daniel Colmenares Oviedo <DtxdF@disroot.org>