Skip to content
Snippets Groups Projects
Select Git revision
  • ae13cdeb4f386f7974e3409b4ee977e9374c77cd
  • master default protected
  • release-1.3.10
  • popover-bootstrap-3.4
  • zf-3.x
  • 3.0.9
  • 3.0.8
  • 1.3.10
  • 3.0.7
  • 3.0.6
  • 3.0.5
  • 3.0.4
  • 3.0.3
  • 3.0.2
  • 3.0.1
  • 3.0.0
  • 1.3.9
  • 1.3.8
  • 1.3.7
  • 1.3.6
  • 1.3.5
  • 1.3.4
  • 1.3.3
  • 1.3.2
  • 1.3.1
25 results

helpers.md

Blame
  • Forked from lib / unicaen / auth
    Source project has a limited visibility.
    Code owners
    Assign users and groups as approvers for specific file changes. Learn more.
    template.header 1.18 KiB
    # -*- text -*-
    ##
    ## templates.conf -- configurations to be used in multiple places
    ##
    ##	$Id: 7b8b44e051c974c1a0a6e27a0cff50e621835df2 $
     
    ######################################################################
    #
    #  Version 2.0 has a useful new feature called "templates".
    #
    #  Use templates by adding a line in radiusd.conf:
    #
    #	$INCLUDE templates.conf
    #
    #  The goal of the templates is to have common configuration located
    #  in this file, and to list only the *differences* in the individual
    #  sections.  This feature is most useful for sections like "clients"
    #  or "home_servers", where many may be defined, and each one has
    #  similar repeated configuration.
    #
    #  Something similar to templates can be done by putting common
    #  configuration into separate files, and using "$INCLUDE file...",
    #  but this is more flexible, and simpler to understand.  It's also
    #  cheaper for the server, because "$INCLUDE" makes a copy of the
    #  configuration for inclusion, and templates are simply referenced.
    #
    #  The templates are defined in the "templates" section, so that they
    #  do not affect the rest of the server configuration.
    #
    #  A section can reference a template by using "$template name"
    #
    templates {