parse

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

Users may not directly execute this command. It is primarily used internally by 66. 66 automatically handles a non-parsed service by invoking the parse command. Users who wish to parse a service again with the -f option should prefer using the reconfigure command.

However, a system administrator might want to parse a service frontend file under construction to ensure everything is functioning correctly without altering the system’s state.

Interface

parser [ -h ] [ -f ] [ -I ] service...

Opens and reads the frontend service file.
Runs a parser on the file.
Writes the parsing result to the /var/lib/66/system/service/svc/foo directory.

The absolute path of the frontend service file can also be set. In this case, the primary path of this absolute path must match /usr/share/66/service or /etc/66/service or $HOME/.66/service directory name e.g /usr/share/66/service/nptd/0.1.1/nptd.

This command handles interdependencies and parse any interdependencies need for the service if they doesn’t parsed yet.

Options

-h: prints this help.
-f: force. Owerwrite an existing parsing result.
-I: do not imports modified configuration files from the previous version used. Refer to Service configuration file for further information.

Usage examples

Parses the frontend file of foo service

66 parse foo

Parses the frontend file of foo service without importing key=value pair previous configuration file

66 parse -I foo

Force to parse again an existing parsing result of foo service

66 parse -f foo

Parses the frontend file of foo service specifying the localization of the frontend file

66 parse /etc/66/service/foo