11 |
requests. Instead of spawning a child each time a request arrives, the |
requests. Instead of spawning a child each time a request arrives, the |
12 |
main server keeps a pool of subprocesses and distributes the requests |
main server keeps a pool of subprocesses and distributes the requests |
13 |
among them. This allows to ensure the stability of the SQL |
among them. This allows to ensure the stability of the SQL |
14 |
connections, make possible the retransmission of the replies when |
connections, and makes possible the retransmission of the replies when |
15 |
duplicate requests arrive. |
duplicate requests arrive. |
16 |
|
|
17 |
* New features |
* New features |
20 |
|
|
21 |
** Multiple remote servers may be defined in a radius realm. |
** Multiple remote servers may be defined in a radius realm. |
22 |
|
|
23 |
|
** New IP allocation strategy. |
24 |
|
|
25 |
|
Included is the plug-in module ipalloc.scm that implements a new |
26 |
|
strategy of allocating framed IP addresses for the users. See file |
27 |
|
doc/README.ipalloc for more info. |
28 |
|
|
29 |
* Changes to configure |
* Changes to configure |
30 |
|
|
31 |
** --enable-snmp gets optional argument 'compat'. |
** --enable-snmp gets optional argument 'compat'. |
45 |
|
|
46 |
This keyword controls the maximum number of handler processes the |
This keyword controls the maximum number of handler processes the |
47 |
dispatcher is allowed to start. It may be used in `option' block |
dispatcher is allowed to start. It may be used in `option' block |
48 |
(see raddb/config.status for an example). The default value is 32. |
(see raddb/config.status for an example). The default value is 8. |
49 |
|
Please notice that each new process consumes 4 file descriptors, so |
50 |
|
make sure you have enough descriptors available before increasing this |
51 |
|
value. |
52 |
|
|
53 |
*** process-idle-timeout |
*** process-idle-timeout |
54 |
|
|
55 |
Each subprocess waits for the request for this amount of time. |
Each subprocess waits for the request for this amount of time. |
56 |
If no request arrives, the subprocess exits. |
If no request arrives, the subprocess exits. |
57 |
|
|
58 |
*** New keyword print-milliseconds |
*** print-milliseconds |
59 |
|
|
60 |
This boolean keyword that can be used in `channel' statement of |
This boolean keyword that can be used in `channel' statement of |
61 |
the `logging' block. It makes radiusd print log timestamps with |
the `logging' block. It makes radiusd print log timestamps with |
62 |
milliseconds. See raddb/config.syntax for examples. |
milliseconds. See raddb/config.syntax for examples. |
63 |
|
|
64 |
** Keywords `spawn' and `usr2delay' are obsolete. |
*** master-read-timeout |
65 |
|
|
66 |
|
This keyword controls the amount of time the server waits when |
67 |
|
reading data from the child process. If no data arrives within this |
68 |
|
time, the child is considered `stuck' and is terminated. By default |
69 |
|
the value of this parameter is zero (no timeout at all). |
70 |
|
|
71 |
|
*** master-write-timeout |
72 |
|
|
73 |
|
Sets the number of seconds to wait for the child input channel to be |
74 |
|
able to receive data from the dispatcher process. If it does not |
75 |
|
become ready within this time , the child is considered `stuck' and |
76 |
|
is terminated. By default the value of this parameter is zero (no |
77 |
|
timeout at all). |
78 |
|
|
79 |
|
** Obsoleted keywords |
80 |
|
|
81 |
|
*** usr2delay (option) |
82 |
|
|
83 |
|
*** spawn (auth,acct,snmp) |
84 |
|
|
85 |
|
The keyword is useless in the new multiprocess model |
86 |
|
|
87 |
|
*** proxy (block statement) |
88 |
|
|
89 |
|
Proxied requests are handled on the common basis with their |
90 |
|
corresponding requests (auth or acct). |
91 |
|
|
|
These keywords are useless with the new multi-process model. |
|
92 |
|
|
93 |
** Use of listen statement is allowed in snmp block. |
** Use of listen statement is allowed in snmp block. |
94 |
|
|
101 |
|
|
102 |
The maximum number of connections to the authentication database equals |
The maximum number of connections to the authentication database equals |
103 |
the maximum number of processes set by `max-processes' statement. The |
the maximum number of processes set by `max-processes' statement. The |
104 |
same holds for the number of connections to accounting the database. |
same holds for the number of connections to the accounting database. |
105 |
|
|
106 |
* Testsuite completely rewritten. |
* Testsuite completely rewritten. |
107 |
|
|