Dave Mason <[EMAIL PROTECTED]> wrote: > Guess I missed where you said that. If my application code doesnt > know or care, something underneath needs to, so I still need to > understand how it works.
Do you really go through the GCC source, to be sure you understand how it works? > I assumed that if I set the type to THREAD_SAFE that each session > will run in its own thread. No. The choice as to threaded or non-threaded is NOT made by the modules. It's made by the administrator, through the configuration files. The THREAD_UNSAFE flag is a flag which the server uses to decide if the module is a "critical section". If the module is NOT thread safe, then the server ensures that only one instance of the module is executed at any one time. The module may run in different threads at different times, but if it's THREAD_UNSAFE, then only one thread is executing the module at a time. > I assume I control the proxy forwarding behavior by returning > different codes from pre_proxy? Do you know where I can find them? The pre_proxy module has the same return codes as all of the other modules. The pre_proxy section is *not* for deciding where to proxy something. It's run once the proxy decision has been made, but before the request is actually proxied. It's purpose is to possibly re-write the proxy request, or maybe to cancel the proxy. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
