[prev in list] [next in list] [prev in thread] [next in thread] 

List:       freeradius-users
Subject:    Re: update disconnect and order of operations
From:       Anatoliy Kushner <cphlpd () gmail ! com>
Date:       2023-07-14 0:22:37
Message-ID: DA7AF048-B7B4-4DFE-9078-AE1E801F8577 () gmail ! com
[Download RAW message or body]

Hi Alan, thank you . That enough for me that update disconnect do not block server \
threads ! 



\ AK

> On 14 Jul 2023, at 09:01, Alan DeKok <aland@deployingradius.com> wrote:
> 
> On Jul 13, 2023, at 7:31 PM, Anatoliy Kushner <cphlpd@gmail.com> wrote:
> > 
> > Hi Alan, please can you explain why this is not possible? 
> 
> I really don't know what you mean.
> 
> If you want to know how FreeRADIUS works, or why it does what it does... the source \
> code is available.  You can read it to see what it does. 
> The "update" disconnect" doesn't block the server threads which process requests.  \
> Your choices are now: 
> a) believe it, and move on with your life
> 
> b) read the source code to understand how it works.
> 
> There isn't much point in (c) - me explaining in detail how the code works.
> 
> So I don't know what kind off explanation you're looking for.  Do I need to explain \
> in detail how the server works, and how asynchronous disconnect packets work?  If \
> so, why not just look at the source code? 
> Alan DeKok.
> 
> -
> List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html


[prev in list] [next in list] [prev in thread] [next in thread]