# GLPI agent configuration

# all defined values match default
# all commented values are examples


#
# Target definition options
#

# send tasks results to a GLPI server
#server = http://server.domain.com/
# send tasks results to a GlpiInventory plugin installed via marketplace
# Read this caution note in documentation to find the right URL:
# https://glpi-agent.readthedocs.io/en/latest/configuration.html#server
#server = http://server.domain.com/glpi/marketplace/glpiinventory/
# send tasks results to a FusionInventory for GLPI server
#server = http://server.domain.com/glpi/plugins/fusioninventory/
# write tasks results in a directory
#local = /tmp

#
# Task definition options
#

# disable software deployment tasks
#no-task = deploy
#tasks = inventory,deploy,inventory

#
# Target scheduling options
#

# maximum delay before first target, in seconds
# Also the maximum delay on network error. Delay on network error starts
# from 60, is doubled at each new failed attempt until reaching delaytime.
delaytime = 3600
# do not contact the target before next scheduled time
lazy = 0

#
# Inventory task specific options
#

# do not list local printers
# no-category = printer
# allow to scan user home directories
scan-homedirs = 0
# allow to scan user profiles
scan-profiles = 0
# save the inventory as HTML
html = 0
# set to 1 to save local inventory as JSON
json = 0
# timeout for inventory modules execution
backend-collect-timeout = 180
# always send data to server
force = 0
# additional inventory content file
additional-content =

# asset name returned
# if 1 (the default), the short hostname is used as asset name
# if 2, the as-is hostname (can be fqdn) is used as asset name
# this feature is not supported on MacOS or Windows
assetname-support = 1

# itemtype (requires GLPI 11 genericity feature support server-side)
# If using "Server" itemtype as generic asset type in GLPI 11+, you can set itemtype to
# "Glpi\CustomAsset\Server" if current computer should be integrated with that type
itemtype = Computer
#itemptype = Glpi\CustomAsset\Server

#
# ESX task specific options
#

# esx-itemtype (requires GLPI 11 genericity feature support server-side)
# If using "ESX" itemtype as generic asset type in GLPI 11+, you can set itemtype to
# "Glpi\CustomAsset\ESX" if esx computers should be integrated with that type
esx-itemtype = Computer
#esx-itemptype = Glpi\CustomAsset\ESX

#
# Package deployment task specific options
#

# do not use peer to peer to download files
no-p2p = 0

#
# Network options
#

# proxy address
proxy =
# user name for server authentication
user =
# password for server authentication
password =
# CA certificates directory
ca-cert-dir =
# CA certificates file
ca-cert-file =
# do not check server SSL certificate
no-ssl-check = 0
# connection timeout, in seconds
timeout = 180

# ssl client certificate filename
ssl-cert-file =
# ssl client private key filename
# (If key file is missing assume it is included in cert file)
ssl-key-file = 

#
# Web interface options
#

# disable embedded web server
no-httpd = 0
# network interface to listen to
httpd-ip =
# network port to listen to
httpd-port = 62354
# trust requests without authentication token
httpd-trust =

#
# Logging options
#

# Logger backend, either Stderr, File or Syslog (Stderr)
logger = stderr
# log file
#logfile = /var/log/glpi-agent.log
# maximum log file size, in MB
#logfile-maxsize = 0
# Syslog facility
logfacility = LOG_USER
# Use color in the console
color = 0

#
# Execution mode options
#

# add given tag to inventory results
tag = 
# debug mode
debug = 0

# time to wait to reload config (0 means no reload, it's default value)
# conf-reload-interval = 0

# Since 2.4, you can include all .cfg files from a folder or any given file
# For example:
#   1. file "conf.d/tag.cfg" contains "tag = 'entity123'"
#      using "include 'conf.d' will set tag to 'entity123'
#   2. file "/etc/production/glpi-tag" contains "tag = 'entity123'"
#      using "include '/etc/production/glpi-tag' will set tag to 'entity123'
# Remark:
#   1. Prefer to use full path to avoid confusion, but be aware relative paths are
#      relative against current config file folder
#   2. A parameter set in included file can be over-rided if set again after the directive
#   3. *.cfg files are read in order in folder, it's better to prefix them with a number
#   4. Package maintainers are encouraged to use this feature to avoid conflict
#      during upgrades after configuration update
#
include "conf.d/"
#include "agent.local"
