Misspellings found by codespell.
#
# v4 also supports a `dictionary { ... }` subsection in a virtual
# server. If the attributes are used only in one virtual server,
-# they shuld be defined there.
+# they should be defined there.
#
#
# ## v3 Compatible names.
#
# All of the attributes have been renamed from v3. This change was
-# necessary in order to support new funtionality in v4. The
+# necessary in order to support new functionality in v4. The
# unfortunate side effect of this change is that all of the names in
# SQL, LDAP, and the "files" module are incompatible with v4.
#
# Yes, we recognize that this process is a bit of work. However, we
# wish to encourage everyone using v4 to upgrade to using the new v4
# features. Our experience shows that if we automatically enable
-# "compatibility functions", then those compatiblity functions will
+# "compatibility functions", then those compatibility functions will
# be used for a decade. So we need to find a balance between
# upgrades and ongoing support. Easy upgrades will mean complex
# ongoing support. Complex upgrades make ongoing support easier, but
#
# The `users` file as located in `raddb/mods-config/files/authorize`. (Livingston-style format).
#
-# See the doc/antora/modules/raddb/pages/mods-config/files/users.adoc file documention for information
+# See the doc/antora/modules/raddb/pages/mods-config/files/users.adoc file documentation for information
# on the format of the input file, and how it operates.
#
# Bring the global hashes into the package scope
our (%RAD_REQUEST, %RAD_REPLY, %RAD_CONFIG, %RAD_STATE);
-# This is hash wich hold original request from radius
+# This hash holds the original request from radius
#my %RAD_REQUEST;
# In this hash you add values that will be returned to NAS.
#my %RAD_REPLY;
-#This is for config items (was %RAD_CHECK in earlier versions)
+# This hash contains config items (was %RAD_CHECK in earlier versions)
#my %RAD_CONFIG;
-# This is the session-sate
+# This is the session state
#my %RAD_STATE;
-# This is configuration items from "config" perl module configuration section
+# This hash contains config items from "config" perl module configuration section
#my %RAD_PERLCONF;
# Multi-value attributes are mapped to perl arrayrefs.
# Number of hosts used at each remote dc (default 0).
# hosts_per_remote_dc = 0
- # Allow remote hosts to be used in no local dc hosts are avaiable and the
+ # Allow remote hosts to be used if no local dc hosts are available and the
# consistency level is 'local_one' or 'local_quorum' (default no).
# allow_remote_dcs_for_local_cl = no
}
#
# If yes, (or auto and libmysqlclient reports warnings are
# available), will retrieve and log additional warnings from
- # the server if an error has occured. Defaults to 'auto'
+ # the server if an error has occurred. Defaults to 'auto'
warnings = auto
}
-- MS SQL lacks a "SELECT FOR UPDATE" statement, and its table
-- hints do not provide a direct means to implement the row-level
- -- read lock needed to guarentee that concurrent queries do not
+ -- read lock needed to guarantee that concurrent queries do not
-- select the same Framed-IP-Address for allocation to distinct
-- users.
--
# This query must update a row when a lease is successfully requested -
# queries that update no rows will result in a "notfound" response to
# the module which by default will give a NAK reply (for DHCPv4).
-# In this example incrementing "counter" is used to acheive this.
+# In this example incrementing "counter" is used to achieve this.
#
update_update = "\
UPDATE ${ippool_table} \
# This query must update a row when a lease is successfully requested -
# queries that update no rows will result in a "notfound" response to
# the module which by default will give a NAK reply. In this example
-# incrementing "counter" is used to acheive this.
+# incrementing "counter" is used to achieve this.
#
update_update = "\
UPDATE ${ippool_table} \
# This query must update a row when a lease is successfully requested -
# queries that update no rows will result in a "notfound" response to
# the module which by default will give a NAK reply. In this example
-# incrementing "counter" is used to acheive this.
+# incrementing "counter" is used to achieve this.
#
update_begin = "commit"
update_update = "\
# This query must update a row when a lease is successfully requested -
# queries that update no rows will result in a "notfound" response to
# the module which by default will give a NAK reply. In this example
-# incrementing "counter" is used to acheive this.
+# incrementing "counter" is used to achieve this.
#
update_update = "\
UPDATE ${ippool_table} \
#
#
-# Is there an exsiting address for this client
+# Is there an existing address for this client
#
alloc_existing = "SELECT address \
FROM ${ippool_table} \
# This query must update a row when a lease is successfully requested -
# queries that update no rows will result in a "notfound" response to
# the module which by default will give a NAK reply. In this example
-# incrementing "counter" is used to acheive this.
+# incrementing "counter" is used to achieve this.
#
update_update = "\
UPDATE ${ippool_table} \
-- this strategy leaves them open and records the NAS reload time in the
-- nasreload table.
--
--- Where applicable, the onus is on the administator to:
+-- Where applicable, the onus is on the administrator to:
--
-- * Consider the nas reload times when deriving a list of
-- active/inactive sessions, and when determining the duration of sessions
processed BOOLEAN DEFAULT false
);
--- You can have more than one record that is identical except for CiscoNASPort if you have a dial peer hungroup
+-- You can have more than one record that is identical except for CiscoNASPort if you have a dial peer huntgroup
-- configured for multiple PRIs.
create UNIQUE index stoptelephonycombo on stoptelephony (AcctTime, nasipaddress, CallID, CiscoNASPort);
-- We therefore do not bother to strip asterisks (*) from timestamps, as you NEED ntp setup
-- unless you don't care about billing at all!
--
--- * Example useage:
+-- * Example usage:
-- insert into mytable values (strip_dot('.16:46:02.356 EET Wed Dec 11 2002'));
--
CREATE OR REPLACE FUNCTION strip_dot (VARCHAR) RETURNS TIMESTAMPTZ AS '
--
-- OPTIONAL Postgresql trigger for FreeRADIUS
--
--- This trigger updates fills in the groupname field (which doesnt come in Accounting packets)
+-- This trigger updates fills in the groupname field (which doesn't come in Accounting packets)
-- by querying the radusergroup table.
-- This makes it easier to do group summary reports, however note that it does add some extra
-- database load to 50% of your SQL accounting queries. If you dont care about group summary
-- this strategy leaves them open and records the NAS reload time in the
-- nasreload table.
--
--- Where applicable, the onus is on the administator to:
+-- Where applicable, the onus is on the administrator to:
--
-- * Consider the nas reload times when deriving a list of
-- active/inactive sessions, and when determining the duration of sessions
-- this strategy leaves them open and records the NAS reload time in the
-- nasreload table.
--
--- Where applicable, the onus is on the administator to:
+-- Where applicable, the onus is on the administrator to:
--
-- * Consider the nas reload times when deriving a list of
-- active/inactive sessions, and when determining the duration of sessions
# Acct-Unique-Session-Id, but this may cause problems
# with NAS that carry Class values across between
# multiple linked sessions. So we rehash class with
- # Acct-Session-ID to provide a truely unique session
+ # Acct-Session-ID to provide a truly unique session
# identifier.
#
# Using a Class/Session-ID combination is more robust
time_delta timeout
#
- # %l is "when the server received the reuest"
+ # %l is "when the server received the request"
#
if (&control.Expiration < %l) {
disallow
#
ENV {
#
- # Set environment varable `FOO` to value '/bar/baz'.
+ # Set environment variable `FOO` to value '/bar/baz'.
#
# NOTE: Note that you MUST use '='. You CANNOT use '+=' to append
# values.
projects / thirdparty / freeradius-server.git / commitdiff
