> > A while ago someone posted that Radius 2.01 had a memory leak (with a
> > patch).
> >
> > I'm currently using a third party radius but want to change to
> > livingston to get the Connect-info (speed) check item.
> >
> > Has the memory leak been fixed (if it did exist)?
>
> It is being fixed in the next version of Radius. It occurs with multiple
> DEFAULT entries in non-forking mode I believe.
Can anyone besides Stephen here confirm that this particular bug occurs
only with Radius 2.01 in non-forking mode?
I'd like to start using the groups stuff in 2.01, but I'd end up with
about two dozen or so default entries, and I wouldn't want to run the
machine out of memory due to a memory leak.
Brian
-
To unsubscribe, email 'majordomo@livingston.com' with
'unsubscribe portmaster-users' in the body of the message.