Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Rialto has customisable configuration settings that can be set either by calling the C++ interface rialto::servermanager::service::create with the ServerManagerConfig structure or by modifying one of JSON configuration files.

...

Config NameDescriptionDefault value
environmentVariablesA list of environment variables that are set in the session servers spawned by the session server manager["XDG_RUNTIME_DIR=/tmp", "GST_REGISTRY=/tmp/rialto-server-gstreamer-cache.bin", "WESTEROS_SINK_USE_ESSRMGR=1"]
extraEnvVariablesA list of environment variables that are added to the existing environmentVariables. These are typically used in rialto-soc.json or rialto-config-overrides.json[""]
sessionServerPathAn absolute path to the sessions session server binary"/usr/bin/RialtoServer"
startupTimeoutMsThe amount of time the session server manager waits for a session server to start. If this time is exceeded, the session server manager stops the server and reports a failure. If the value is set to 0, there is no time limit, and the manager will wait indefinitely.0
healthcheckIntervalInSeconds

Specifies how often health check messages are sent.

5
numOfPingsBeforeRecovery

Specifies how many consecutive failed pings are required before a recovery action is triggered.

3
socketPermissions

Specifies the permissions for the session management socket, expressed in octal permissions.

666
socketOwnerSpecifies the owner of the session management socket. If it's blank, it will be inherited from the parent process.""
socketGroupSpecifies the group ownership of the session management socket. If it's blank, it will be inherited from the parent process.""
numOfPreloadedServersThe amount of preloaded servers.1
logLevelLog level of all Rialto components.

1 - ERROR
2 - WARNING and above
3 - MILESTONE and above
4 - INFO and above

5 - DEBUG and above
3

...

To allow more flexible environment variable management, repeated environmentVariables will also overwrite extraEnvVariables from the previous configuration settings. Additionally, if there are environment variables with the same names in both environmentVariables and extraEnvVariables, the values from extraEnvVariables will take priority and be used.

Examples:

ExampleFinal environment variables set in the Session ServerNote

/etc/sky/rialto-config.json: environmentVariables = ["env1=1"], extraEnvVariables = ["env2=2"]
/etc/rialto-soc.json: environmentVariables = ["env3=3"]

["env3=3"]environmentVariables
from
from /etc/rialto-soc.json overriden both 
environmentVariables and
environmentVariables and extraEnvVariables from /etc/sky/rialto-config.json
/etc/sky/rialto-config.json: environmentVariables = ["env1=1"], extraEnvVariables = ["env2=2"]
/etc/rialto-soc.json: extraEnvVariables = ["env3=3"]
/opt/persistent/sky/rialto-config-overrides.json: extraEnvVariables = ["env4=4"]

["env1=1", "env4=4"]
extraEnvVariables from
extraEnvVariables from the /opt/persistent/sky/rialto-config-overrides.json and environmentVariables from /etc/sky/rialto-config.json are combined
/etc/sky/rialto-config.json: environmentVariables = ["env1=1", "env2=2"]
/etc/rialto-soc.json:
extraEnvVariables = ["env1=3"]
["env1=3", "env2=2"]env1 is defined in both environmentVariables and extraEnvVariables, the value from extraEnvVariables will be used.