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-parser.md 2.34 KiB

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

66

Software

obarun.org

66-parser

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

Interface

    66-parser [ -h ] [ -z ] [ -v verbosity ] [ -f ] [ -I ] 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 %%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.

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

  • -I : do not imports modified configuration files from the previous version used. Refer to Service configuration file for further information.

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 %%service_admconf%%/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.