[Radmind-commit] radmind/man radmind.8,1.43,1.44

[Andrew M. <fit...@us...>]

Update of /cvsroot/radmind/radmind/man
In directory sc8-pr-cvs9.sourceforge.net:/tmp/cvs-serv400/man

Modified Files:
	radmind.8 
Log Message:
Accepted patch [ 1919220 ]: Includes in config file.


Index: radmind.8
===================================================================
RCS file: /cvsroot/radmind/radmind/man/radmind.8,v
retrieving revision 1.43
retrieving revision 1.44
diff -C2 -d -r1.43 -r1.44
*** radmind.8	29 Nov 2007 17:21:59 -0000	1.43
--- radmind.8	24 Mar 2008 18:43:42 -0000	1.44
***************
*** 80,83 ****
--- 80,106 ----
  listed in their base command file as determined by the config
  file.
+ .sp
+ _RADMIND_PATH/config can include other config files using the keyword
+ "@include", which can be used in two ways. The first is a simple include
+ of another file. If the path does not begin with a slash (/), the path is
+ interpreted as being relative to _RADMIND_PATH. For example:
+ .sp
+ .br
+ 	@include configs/ldap-servers.config
+ .br
+ .sp
+ which would cause every connecting client to be checked against the contents
+ of _RADMIND_PATH/configs/ldap-servers.config. The @include keyword can also
+ take an optional third argument, a wildcard pattern limiting which clients
+ will read the included config file. For example:
+ .sp
+ .br
+ 	@include configs/kerberos-kdcs.config *.kerberos.example.edu
+ .br
+ .sp
+ would cause only clients with FQDNs matching '*.kerberos.example.edu' to
+ read the included file. The wildcard is checked, in order, against the
+ client's certificate CN (if the client presents one), the client's
+ fully-qualified domain name, and the client's IP address.
  .SH DIRECTORY STRUCTURE
  .TP 19