Marcelo Ferreira [EMAIL PROTECTED] wrote:
I tested the 20020203 snapshot with the _r() changes.
I ran then server without the -s option (radiusd -p 1812 ) and it cored
dump:
sigh These problems are a real pain to track down.
If I run it with -s (radiusd -s -p 1812) works fine.
Yeah,
Miquel van Smoorenburg [EMAIL PROTECTED] wrote:
Well, you should be able to link against thread-safe variants of
those functions, right? I mean, strtok() is obviously not
thread safe, but localtime() should be.
Nope. Log into a *BSD box. The thread-safe variant of localtime()
is
I have been experiencing crashes as well under high accounting load
(Solaris 7 , mysql accounting). It appears that the use of non thread-safe
library functions are responsible for this. I have replaced all the
localtime() and ctime() calls with their POSIX thread safe counterparts
: Eddie Stassen [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Friday, February 01, 2002 2:25 PM
Subject: Re: Thread issue - Possible fix
I have been experiencing crashes as well under high accounting load
(Solaris 7 , mysql accounting). It appears that the use of non thread-safe
library functions
- Original Message -
From: Eddie Stassen [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Friday, February 01, 2002 2:25 PM
Subject: Re: Thread issue - Possible fix
I have been experiencing crashes as well under high accounting load
(Solaris 7
Eddie Stassen [EMAIL PROTECTED] wrote:
It appears that the use of non thread-safe library functions are
responsible for this.
Uh, yeah. Why didn't I think of that.
Sorry...
I don't know how applicable these changes are to other OS's (Linux), but
perhaps someone running FR on linux
On Fri, Feb 01, 2002 at 10:52:49AM -0500, [EMAIL PROTECTED] wrote:
Eddie Stassen [EMAIL PROTECTED] wrote:
It appears that the use of non thread-safe library functions are
responsible for this.
[...]
The changes MUSt be made for safety. I'll take a look at doing some
of the work over the
In article [EMAIL PROTECTED],
[EMAIL PROTECTED] wrote:
Eddie Stassen [EMAIL PROTECTED] wrote:
It appears that the use of non thread-safe library functions are
responsible for this.
Uh, yeah. Why didn't I think of that.
Sorry...
Well, you should be able to link against thread-safe
