# There are 3 ways to run dcgm-exporter.
# - embedded (default):
#	nv-hostengine is run as an internal part of dcgm-exporter utilizing the
#	the shared libraries provided by the datacenter-gpu-manager package.
# - standalone client:
#	dcgm-exporter connects to the nv-hostengine via IP or Unix socket
#	passed via --connect={ip:port|file} [--socket='isSocket']. In the socket
#	case the file arg must be the same as the arg to the --domain-socket
#	parameter for the nv-hostengine instance in question.
# - mixed:
#	dcgm-exporter forks a nv-hostengine process and connects to it via a
#	Unix socket named /tmp/dcgm* . When dcgm-exporter gets shutdown, it tries
#	to shutdown the nv-hostengine process first using 'nv-hostengine --term'.
# However, right now the 'embedded' mode is hard coded. So running the dcgm
# service is just overhead, as long as you wanna use it for metrics, only.

# Any options to pass verbatim to the server. See 'dcgm-exporter -h'.
ARGS=""

# Check operational state e.g. via http://localhost:9400/metrics