Skip to content
Snippets Groups Projects
Select Git revision
  • master default
  • dev
  • resolve
  • parser
  • patch-1
  • async
  • boot
  • state
  • 0.8.0.2
  • 0.8.0.1
  • 0.8.0.0
  • 0.7.2.1
  • 0.7.2.0
  • 0.7.1.1
  • 0.7.1.0
  • 0.7.0.2
  • 0.7.0.1
  • 0.7.0.0
  • 0.7.0.0-preprod-rev2
  • 0.7.0.0-preprod-rev1
  • 0.7.0.0-preprod
  • 0.7.0.0-beta-3
  • 0.7.0.0-beta-2
  • 0.7.0.0-beta
  • v0.6.2.0
  • v0.6.1.3
  • v0.6.1.2
  • v0.6.1.1
28 results
Blame Permalink
66-init.md 3.05 KiB

title: The 66 Suite: 66-init author: Eric Vidal eric@obarun.org

66

Software

obarun.org

66-init

This command initiates services from a given tree at a live directory.

Interface

    66-init [ -h help ] [ -z ] [ -v verbosity ] [ -l live ] [ -t tree ] classic|database|both

This tool expects to find an already created scandir directory at live location. The scandir does not need to be necessarily running depending on the provided options. Administrators should invoke 66-init only once.

Exit codes

  • 0 success
  • 100 wrong usage
  • 111 system call failed

Options

  • -h : prints this help.

  • -z : use color.

  • -v verbosity : increases/decreases the verbosity of the command.

    • 1 : only print error messages. This is the default.
    • 2 : also print warning messages.
    • 3 : also print tracing messages.
    • 4 : also print debugging messages.

  • -l live : changes the supervision directory of service to live. By default this will be %%livedir%%. The default can also be changed at compile time by passing the --livedir=live option to ./configure. An existing absolute path is expected and should be within a writable and executable filesystem - likely a RAM filesystem—see 66-scandir.

Arguments

  • classic : only initiate all classic services from tree at live location.

  • datatabe : only initiate all bundle and atomic services from tree at live location.

  • both : initiate all classic services and all bundle and atomic services from tree at live location.

Initialization process

The tool will make an exact copy of all classic service files and directories of the tree inside a scandir directory at live. By default %%livedir%%/scandir/UID is created if it does not exist yet, where UID is the uid of the current owner of the process. The scandir does not need to be necessarily running. This is useful at boot time to initiate an early service before starting the scandir. Once the scandir starts—see 66-scandir -u option, the already present services start automatically.

If the scandir is running, you should invoke a 66-scanctl reload command to inform it about the changes.

Bundle, atomic services

The tool will automatically invoke s6-rc-init -l live -c compiled -p prefix, where, by default, live translates to %%livedir%%/tree/UID/tree and compiled to %%system_dir%%/66/system/tree/servicedirs/db/tree or $HOME/%%user_dir%%/system/tree/servicedirs/db/tree depending on the owner of the process and the prefix of the name of the tree. If it doesn't exist yet live is created in the process. For these services the scandir must be running. This tool like any other 66 tool can be invoked with user permissions.