66

obarun.org

66-parser

Parses a frontend service file and writes the result to a directory.

Interface

    66-parser [ -h ] [ -z ] [ -v verbosity ] [ -f ] [ -c|m|C ] service destination

• Opens and reads the frontend service file.
• Runs a parser on the file.
• Writes the parsing result to the destination directory.

An absolute path is expected for either service and destination.

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 /run/66. 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.

• -f : force. Owerwrite an existing parsing result at destination.

• -c : only appends new key=value pairs to the environment configuration file from frontend file.

• -m : appends new key=value and merges existing one to the environment configuration file from frontend file.

• -C : overwrite it environment configuration file from frontend file.

Notes

66-parser will not try to read and parse any services declared under the @contents, @depends, @optsdepends or @extdepends key of the given frontend file even for a service module type. This tool is mainly intended for debugging purposes and to see the result of a parsing process before actually enabling the service on the system. The tool uses the exact same parser as 66‑enable which by default writes the configuration file to /etc/66/conf/service_name. As a consequence any corresponding existing file will be overwritten. To avoid this, it writes the configuration file to the destination/env/ directory and adjust the resulting run/finish file to match the configuration file path.