...and what information are you providing? I see nothing with this report
(ps if this is with an version, then the first thing you do is try the latest
release as it may have already been fixed)
alan
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Hi I am just reporting a segfault.
Regards,
Prateek
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
On 20/07/12 14:16, Prateek Kumar wrote:
Hi,
Can reproduce in 2.1.10 also. Currently can not upgrade. So will
try in some other system.
Do you actually want/think you need a duplicate client and if so, why?
Or are you just reporting the segfault?
-
List info/subscribe/unsubscribe? See ht
Hi,
Can reproduce in 2.1.10 also. Currently can not upgrade. So will try
in some other system.
Regards,
Prateek
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Prateek Kumar wrote:
> I have 2 ldap modules which are selected by unlang logic and I
> have configured my certificates as default. Now when I put a dupticate
> client entry in clients.conf file & then kill the radius server I got a
> error like *** glibc detected *** radiusd: free(): inva
Hi
On Fri, Jul 20, 2012 at 05:09:51PM +0530, Prateek Kumar wrote:
> error like *** glibc detected *** radiusd: free(): invalid pointer:
> 0xb778e994. Also some time I get the error like munmap_chunk(): invalid
> pointer. If I remove the duplicate client entry then I don't see the error.
So remove
Hi,
I have 2 ldap modules which are selected by unlang logic and I
have configured my certificates as default. Now when I put a dupticate
client entry in clients.conf file & then kill the radius server I got a
error like *** glibc detected *** radiusd: free(): invalid pointer:
0xb778e994.
7 matches
Mail list logo
