Gary Gatten wrote:
>
> FBSD allows one to easily change the scheduler, MAYBE that would help?
>
I've tried changing scheduler, but alas to no avail.
It was worth a shot though.
/ Danial
--
View this message in context:
http://freeradius.1045715.n5.nabble.com/Freeradiusd-2-1-8-tp3346801p423
Danial wrote:
> Does this mean we shouldn't expect this bug to be fixed in new releases,
> unless the code gets rewritten?
Or unless someone tracks it down and submits a patch.
It's open source software. There's no need to wait for the bug to
magically get fixed. People *can* contribute.
, 2011 9:48 AM
To: freeradius-users@lists.freeradius.org
Subject: Re: Freeradiusd 2.1.8
Alan DeKok-2 wrote:
>
> It's something which is seen only on FreeBSD. As far as I can tell,
> it's a race condition in the threading code. It's difficult to track
> down and debug,
Alan DeKok-2 wrote:
>
> It's something which is seen only on FreeBSD. As far as I can tell,
> it's a race condition in the threading code. It's difficult to track
> down and debug, unfortunately.
>
> Given the level of complexity of the current code, it's probably best
> to re-write it, to
Brian Carpio wrote:
> No one was on the box doing anything… I was looking into this issue with
> google and came across a thread back in Nov 2009 about an issue a user
> was experiencing with radiusd 2.1.8, and this user send some gdb dumps
> to the development team… I can’t seem to recreate the is
Brian Carpio writes:
> I have a production environment which is running freeradiusd 2.1.8 and
> last night in the logs I see the following message
>
> Sat Jan 1 20:11:24 2011 : Error: Mon Jan 10 17:04:58 2011 : Info: Exiting
> normally.
>
> No one was on the box doing anyt
I have a production environment which is running freeradiusd 2.1.8 and last
night in the logs I see the following message
Sat Jan 1 20:11:24 2011 : Error: Mon Jan 10 17:04:58 2011 : Info: Exiting
normally.
No one was on the box doing anything... I was looking into this issue with
google and
7 matches
Mail list logo
