Skip to content
Snippets Groups Projects
Select Git revision
  • 645aee5c705f8c02df2ce1f233124e994bdda66c
  • master default protected
  • b24
  • ll-workflow
  • alc-scindage-donnees-pj
  • FJ_LL_Tbl_Contrat
  • alc-docker-node
  • ll-apiplatform
  • php84
  • ll-rgpd
  • b23
  • alc-filtre-type-intervenant
  • ll-sans-mdb5
  • formules-ancienne-infra
  • ll-formules
  • alc-intervenant-dmep
  • ll-suppr-v_vol-s
  • b20
  • ll-postgresql
  • b23.0.1
  • b22
  • 24.8
  • 24.7
  • 24.6
  • 24.5
  • 24.4
  • 24.3
  • 24.2
  • 24.1
  • 24.0
  • 23.15
  • 24.0-beta19
  • 24.0-beta18
  • 24.0-beta17
  • 24.0-beta16
  • 24.0-beta15
  • 24.0-beta14
  • 24.0-beta13
  • 23.14
  • 24.0-beta12
  • 24.0-beta11
41 results

NewOseForm.php

Blame
  • 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 {