On 11/20/2012 09:08 PM, Ricardo Martinez wrote: > This make me think, is there any queque in Radiator for the > Authorization packets? Can I see this queque?, can I take measures?
The queue is UDP socket buffer the operating system maintains. Radiator reads requests from the socket one by one. In other words, if there are multiple incoming requests, it does not first read them all and then start processing them. You can try e.g., 'netstat -ulpn' on Linux to see socket buffer (Recv-Q) usage. Try e.g. kill -STOP <radiusd pid> and then use radpwtst to send a request. Since radiusd is stopped you will see how the Recv-Q count grows. When you do kill -CONT <radiusd pid> radiusd will read the requests and Recv-Q is empty again. > For example, if 10 or 20 Access-Request packet arrives to Radiator, how > are processed? The are processed one by one from the incoming socket. You should turn on 'LogMicroseconds' global option and then test with radpwtst and other clients. With Trace 4 you will see exactly how long DB query takes when you compare the debug log microsecond timestamps. Thanks, Heikki -- Heikki Vatiainen <h...@open.com.au> Radiator: the most portable, flexible and configurable RADIUS server anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald, Platypus, Freeside, TACACS+, PAM, external, Active Directory, EAP, TLS, TTLS, PEAP, TNC, WiMAX, RSA, Vasco, Yubikey, MOTP, HOTP, TOTP, DIAMETER etc. Full source on Unix, Windows, MacOSX, Solaris, VMS, NetWare etc. _______________________________________________ radiator mailing list radiator@open.com.au http://www.open.com.au/mailman/listinfo/radiator
