It would be difficult for me to turn off the simultaneous use because I have that attribute set for all our users in the sql database. I don't want to muck around too much with a production server, and I haven't seen this happen on my development environment.
I've gone ahead and turned on core dumping in the radiusd.conf file. Looking in the log files it looks like it might have crashed overnight, but since I'm now running it with radwatch radiusd is still up and running. I can't find the core file anywhere, where would it have put it if it did do a core dump?
Is there any performance issues running radius with core dumping on? The config file makes it seem like there might be.
Also now that I'm running with radwatch, I now see radiusd has the attribute -f, I assume radwatch stuck that in there, because I know I didn't. Is this causing any performance issues? It it preventing radiusd from spawning off new children if need be?
- freeradius-0.5 crashing Jeremy Kusnetz
- Re: freeradius-0.5 crashing Chris Parker
- Re: freeradius-0.5 crashing Alan DeKok
- Re: freeradius-0.5 crashing Mike Cathey
- Re: freeradius-0.5 crashing D. Duccini
- Re: freeradius-0.5 crashing Alan DeKok
- Re: freeradius-0.5 crashing Jeremy Kusnetz
- Re: freeradius-0.5 crashing Alan DeKok
- RE: freeradius-0.5 crashing Stefan Immel
- Re: freeradius-0.5 crashing Alan DeKok
- RE: freeradius-0.5 crashing Stefan Immel
- Re: freeradius-0.5 crashing Giovanni P. Tirloni
- session timeout attribute Hooman Amini
- Re: session timeout attribute Rodrigo Gonzalez
- Re: session timeout attribute Hooman Amini
- Re: session timeout attribu... Rodrigo Gonzalez
- Re: session timeout att... Hooman Amini
