Running ntlm_auth as a connection pool

[Arnab Roy]

   Hi Mathew/Alan,

   Just a small additional question, so as it stands unless I completely
   re-do this whole piece , I am highly unlikely to get out of this hole.
   So as a temporary suggestion I have got plenty of CPU , DISK IO and
   Memory resources. Fr is barely using anything , any parameters I can
   change so FR uses the spare hardware resources to process the
   concurrent mschap requests ?


   Many Thanks
   Arnab
   Sent: Thursday, August 31, 2017 at 12:29 PM
   From: "Matthew Newton" <matthew at newtoncomputing.co.uk>
   To: "FreeRadius users mailing list"
   <freeradius-users at lists.freeradius.org>
   Subject: Re: Running ntlm_auth as a connection pool
   On 31 August 2017 11:26:32 BST, Arnab Roy <arnabroy at mail.com> wrote:
   >Thanks for the suggestion I am with you on using native ldap, I guest
   I
   > can just do an on the fly ldap xlat to get the correct username info.
   > However, I forgot to mention another challenge! Our winbind socket is
   > sitting somewhere else as we run multiple instances of winbind
   IIRC the socket location is hard coded into libwbclient at Samba
   compile time. FreeRADIUS can't change it.
   --
   Matthew
   -
   List info/subscribe/unsubscribe? See
   [1]http://www.freeradius.org/list/users.html

References

   1. http://www.freeradius.org/list/users.html