LOTS ADDED!!!

Reporting output and logging configurations are now included here,
along with more/better inline documentation on how to set up this file.
This commit is contained in:
Cort Buffington 2013-12-15 10:05:34 -06:00
parent b461bc9240
commit 2be203cb8d
1 changed files with 44 additions and 3 deletions

View File

@ -1,7 +1,48 @@
# DMRLink Sample Configuration File
# DMRLink SAMPLE CONFIGURATION FILE
#
# Rename to dmrlink.cfg and add your information
# # GLOBAL CONFIGURATION ITEMS
# There are no global options at this time
#
[GLOBAL]
# STDOUT REPORTING CONFIG
# Enabling "REPORT_PEERS" will cause a print-out of the peers in each
# IPSC each time the periodic reporting loop runs. Likewise, the
# additional features listed will cause that list to either include
# or not include MODE and/or SERVICE FLAG details.
#
[REPORTS]
REPORT_PEERS: 1
PEER_REPORT_INC_MODE: 0
PEER_REPORT_INC_FLAGS: 0
# SYSTEM LOGGER CONFIGURAITON
# This allows the logger to be configured without chaning the individual
# python logger stuff in dmrlink.py. LOG_FILE should be a complete
# path/filename for *your* system. LOG_HANDERLS may be any of the
# following, please, no spaces in the list if you use several:
# console
# console-timed
# file
# file-timed
# syslog
# LOG_LEVEL may be any of the standard syslog logging levels, though
# as of now, DEBUG, INFO, WARNING and CRITICAL are the only ones
# used.
#
[LOGGER]
LOG_FILE: /tmp/dmrlink.log
LOG_HANDLERS: console,file-timed
LOG_LEVEL: DEBUG
# CONFIGURATION FOR IPSC NETWORKS
#
# [NAME] The name you want to use to identify the IPSC instance
# [NAME] The name you want to use to identify the IPSC instance (use
# something better than "IPSC1"...)
# ENABLED: Should we communiate with this network? Handy if you need to
# shut one down but don't want to lose the config
# RADIO_ID: This is the radio ID that DMRLink should use to communicate
@ -14,7 +55,7 @@
# MASTER_PORT: UDP port of the IPSC master
#
# ...Repeat the block for each IPSC network to join.
#
[IPSC1]
ENABLED: True
RADIO_ID: 1