John Dennis writes:
> * FreeRADIUS has way too much churn for a critical system
> service. Think about other system services, how often do you see
> kerberos, bind, iptables, pam, MySQL, etc. going through significant
> revisions? Are the administrators of those services constantly being
> told t
Hi,
> This is a production server,
> What is the latest stable version to use?
'stable' is all in the mind ;-)
we run the latest 2.1.11 from GIT on our production servers (nee 2.1.12)
and a 3.x release on a couple of test servers to test/see the new functions.
alan
-
List info/subscribe/unsubscr
Hi,
> > * FreeRADIUS has no notion of a "stable release". Many projects maintain
'stable' or 'stale'
if you go for the 'stable' release of most daemons you will not
have the ability to do certain things, the latest version will have those
abilities.
in the FR case, the most 'tested' version i
John Dennis wrote:
> FreeRADIUS has some problems which other projects have avoided.
Sure. The reasons are pretty straightforward. The contribution from
the community is small. The people who contribute get few rewards, and
lots of arrows. The people who complain don't contribute.
It's re
Upgraded freeradius to 2.1.11 (built from source)
Don't use 2.1.11 it segfaults, checkout the head of the 2.1.X branch in git
Notice how I DIDN'T suggest upgrading to 2.1.11, but to v2.1.x of git
branch? There's a reason for that, and you just found out the hard
way.
"Houston, we have a p
ng list
> Subject: Re: segmentation fault freeradius 2.1.7 using rlm_sql
>
> On Tue, Aug 2, 2011 at 2:27 PM, Amir Tal wrote:
>> Upgraded freeradius to 2.1.11 (built from source)
>>
>> This time it brought the whole machine down:
>
> Notice how I DIDN'T su
02, 2011 11:02 AM
To: FreeRadius users mailing list
Subject: Re: segmentation fault freeradius 2.1.7 using rlm_sql
On Tue, Aug 2, 2011 at 2:27 PM, Amir Tal wrote:
> Upgraded freeradius to 2.1.11 (built from source)
>
> This time it brought the whole machine down:
Notice how I DIDN&
On Tue, Aug 2, 2011 at 2:27 PM, Amir Tal wrote:
> Upgraded freeradius to 2.1.11 (built from source)
>
> This time it brought the whole machine down:
Notice how I DIDN'T suggest upgrading to 2.1.11, but to v2.1.x of git
branch? There's a reason for that, and you just found out the hard
way.
--
F
On 2 Aug 2011, at 09:27, Amir Tal wrote:
> Upgraded freeradius to 2.1.11 (built from source)
Don't use 2.1.11 it segfaults, checkout the head of the 2.1.X branch in git
-Arran
Arran Cudbard-Bell
a.cudba...@freeradius.org
RADIUS - Half the complexity of Diameter
-
List info/subscribe/unsubscr
-bounces+amir=ccc.co...@lists.freeradius.org] On Behalf
Of Alan DeKok
Sent: Wednesday, July 27, 2011 4:33 PM
To: FreeRadius users mailing list
Subject: Re: segmentation fault freeradius 2.1.7 using rlm_sql
Amir Tal wrote:
> For some unknown reason radiusd keeps getting segmentation faults, ev
age-
> From: freeradius-users-bounces+amir=ccc.co...@lists.freeradius.org
> [mailto:freeradius-users-bounces+amir=ccc.co...@lists.freeradius.org] On
> Behalf Of Alan DeKok
> Sent: Wednesday, July 27, 2011 4:33 PM
> To: FreeRadius users mailing list
> Subject: Re: segmentation fau
, 2011 4:33 PM
To: FreeRadius users mailing list
Subject: Re: segmentation fault freeradius 2.1.7 using rlm_sql
Amir Tal wrote:
> For some unknown reason radiusd keeps getting segmentation faults, every few
> days and even after several hours of work.
Upgrade.
Alan DeKok.
-
List info/sub
Amir Tal wrote:
> For some unknown reason radiusd keeps getting segmentation faults, every few
> days and even after several hours of work.
Upgrade.
Alan DeKok.
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Hi all,
freeRADIUS version 2.1.7
(package freeradius2 on centos 5.6)
Radius is configured to store user info (auth) in ldap - running on same
machine as freeradius,
and use rlm_sql for accounting info (and simultaneous use checks) - running on
remote machine.
For some unknown reason radiusd ke
14 matches
Mail list logo
