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-frontend.md 29.05 KiB

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

66

Software

obarun.org

The frontend service file

The s6 programs use different files. It is quite complex to understand and manage the relationship between all those files. If you're interested in the details you should read the documentation for the s6 servicedir and also about classic and module services. The frontend service file of 66 program allows you to deal with all these different services in a centralized manner and in one single location.

By default 66 program expects to find service files in %%service_system%% and %%service_adm%% for root user, %%service_system%%/user and %%service_adm/user%% for regular accounts. For regular accounts, $HOME/%%service_user%% will take priority over the previous ones. Although this can be changed at compile time by passing the --with-system-service=DIR, --with-sysadmin-service=DIR and --with-user-service=DIRoption to ./configure.

The frontend service file has a format of INI with a specific syntax on the key field. The name of the file usually corresponds to the name of the daemon and does not have any extension or prefix.

The file is made of sections which can contain one or more key value pairs where the key name can contain special characters like - (hyphen) or _ (low line) except the character @ (commercial at) which is reserved.

You can find a prototype with all valid section and all valid key=value pair at the end of this document.