<commit_before>#
# This properties file allows you to set global properties for the opennms
# application.  These properties will be set as system properties at the
# beginning of Java startup.  Any properties set on the Java command-line
# with -Dproperty=value will be overridden by these values.
#

# ###### SNMP ######
# OpenNMS provides two different SNMP implementations.  JoeSNMP is the
# original OpenNMS # SNMP Library and provides SNMP v1 and v2 support.
# SNMP4J is a new 100% Java SNMP library # that provides support for SNMP
# v1, v2 and v3.  
#
# To enable the JoeSnmp library uncomment the following line.
#org.opennms.snmp.strategyClass=org.opennms.netmgt.snmp.joesnmp.JoeSnmpStrategy
#
# The SNMP4J library is currently the default.  But can also be set with
# the following line.
#
# Default:
#org.opennms.snmp.strategyClass=org.opennms.netmgt.snmp.snmp4j.Snmp4JStrategy
#

# The world is full of buggy SNMP agents.  We can work around many of their
# quirks by extending various SMI classes from SNMP4J.  The following property
# must be set in order for any of these workarounds to be enabled.
org.snmp4j.smisyntaxes=opennms-snmp4j-smisyntaxes.properties

# When debugging SNMP problems when using the SNMP4J library, it's a great
# help to receive runtime exceptions from SNMP4J. These exceptions almost
# always indicate a problem with an SNMP agent, but if they are filling up
# the logs you can disable them by changing the following line so that
# the value is "false".
org.opennms.snmp.snmp4j.forwardRuntimeExceptions=true

# Net-SNMP agents prior to release 5.4.1 on 64-bit platforms exhibit a bug
# that causes the discovery of a node's interfaces to fail. A workaround has
# been made that helps SNMP4J cope with this bug. If for some reason you need
# to disable this workaround, comment out the following line.
org.opennms.snmp.workarounds.allow64BitIpAddress=true

# ###### DATA COLLECTION ######
# On very large systems the OpenNMS default mechanism of storing one data
# source per RRD file can be very I/O Intensive.  Many I/O subsystems fail
# to keep up with the vast amounts of data that OpenNMS can collect in this
# situation.  We have found that in those situations having fewer large files
# with multiple data sources in each performs better than many smaller files,
# each with a single data source.  This option enables all of the data sources
# belonging to a single collection group to be stored together in a single
# file.  To enable this setting uncomment the below line and change it to
# 'true'.  Also note that the snmp-graph.properties will need to change as
# it indicates which files need to exist for each graph.  Look in 
# $OPENNMS_HOME/etc/examples/store-by-group-snmp-graph.properties for an
# example of the changes.<commit_msg>remove comment about custom snmp-graphs.properties for storeByGroup=true because is no longer needed.<commit_after>#
# This properties file allows you to set global properties for the opennms
# application.  These properties will be set as system properties at the
# beginning of Java startup.  Any properties set on the Java command-line
# with -Dproperty=value will be overridden by these values.
#

# ###### SNMP ######
# OpenNMS provides two different SNMP implementations.  JoeSNMP is the
# original OpenNMS # SNMP Library and provides SNMP v1 and v2 support.
# SNMP4J is a new 100% Java SNMP library # that provides support for SNMP
# v1, v2 and v3.  
#
# To enable the JoeSnmp library uncomment the following line.
#org.opennms.snmp.strategyClass=org.opennms.netmgt.snmp.joesnmp.JoeSnmpStrategy
#
# The SNMP4J library is currently the default.  But can also be set with
# the following line.
#
# Default:
#org.opennms.snmp.strategyClass=org.opennms.netmgt.snmp.snmp4j.Snmp4JStrategy
#

# The world is full of buggy SNMP agents.  We can work around many of their
# quirks by extending various SMI classes from SNMP4J.  The following property
# must be set in order for any of these workarounds to be enabled.
org.snmp4j.smisyntaxes=opennms-snmp4j-smisyntaxes.properties

# When debugging SNMP problems when using the SNMP4J library, it's a great
# help to receive runtime exceptions from SNMP4J. These exceptions almost
# always indicate a problem with an SNMP agent, but if they are filling up
# the logs you can disable them by changing the following line so that
# the value is "false".
org.opennms.snmp.snmp4j.forwardRuntimeExceptions=true

# Net-SNMP agents prior to release 5.4.1 on 64-bit platforms exhibit a bug
# that causes the discovery of a node's interfaces to fail. A workaround has
# been made that helps SNMP4J cope with this bug. If for some reason you need
# to disable this workaround, comment out the following line.
org.opennms.snmp.workarounds.allow64BitIpAddress=true

# ###### DATA COLLECTION ######
# On very large systems the OpenNMS default mechanism of storing one data
# source per RRD file can be very I/O Intensive.  Many I/O subsystems fail
# to keep up with the vast amounts of data that OpenNMS can collect in this
# situation.  We have found that in those situations having fewer large files
# with multiple data sources in each performs better than many smaller files,
# each with a single data source.  This option enables all of the data sources
# belonging to a single collection group to be stored together in a single
# file.  To enable this setting uncomment the below line and change it to
# 'true'.  Also note that the snmp-graph.properties will need to change as
# it indicates which files need to exist for each graph. 
{'fraction_non_alphanumeric': 0.05825242718446602, 'fraction_numerical': 0.009349154980222941, 'mean_word_length': 4.298095238095238, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '4888812', 'n_tokens_mistral': 1599, 'n_tokens_neox': 1570, 'n_words': 779}