Blame SOURCES/net-snmp-5.7.2-documentation.patch

936e0f
diff -urNp a/man/snmp_config.5.def b/man/snmp_config.5.def
936e0f
--- a/man/snmp_config.5.def	2017-06-26 11:30:42.728527539 +0200
936e0f
+++ b/man/snmp_config.5.def	2017-06-26 11:33:19.766436329 +0200
936e0f
@@ -179,14 +179,28 @@ during normal configuration file process
936e0f
 .RS
936e0f
 .nf
936e0f
 # include site specific config
936e0f
-include site.conf
936e0f
+includeFile site.conf
936e0f
 .RE
936e0f
 .PP
936e0f
-This will search every directory in the configuration path for files
936e0f
-named site.conf, and will process those files before returning to the
936e0f
-processing of the original file. Note that if '.conf' is omitted,
936e0f
-it will be appended. That is, all configuration files must end
936e0f
-in '.conf'.
936e0f
+This will load the specified configuration file. The
936e0f
+path to file must be either absolute, starting with '/',
936e0f
+or relative. The relative path is then relative to the directory
936e0f
+where the parent file with 'includeFile' directive resides.
936e0f
+.PP
936e0f
+The included file name does not need to have '.conf' suffix.
936e0f
+.PP
936e0f
+.RS
936e0f
+.nf
936e0f
+# include a all *.conf files in a directory
936e0f
+includeDir /etc/snmp/config.d
936e0f
+.RE
936e0f
+.PP
936e0f
+This will search specified directory for all files with '.conf'
936e0f
+suffix and process them as if they were included using includeFile
936e0f
+directive. The configuration files are not processed in any particular
936e0f
+order.
936e0f
+.PP
936e0f
+The specified directory must be absolute directory path.
936e0f
 .SH "API INTERFACE"
936e0f
 .PP
936e0f
 Information about writing C code that makes use of this system in
936e0f