Too many open files EAP-TLS

I've got a client's server running FreeRADIUS 2.1.10 from source. Linux kernel 2.6.35.7, heavily customized Slackware 13.0 So far, not using chroot, running as root. It's a EAP-TLS setup with OpenSSL verifying via 'client = ', tmpdir = /tmp/radiusd Everything has been fine for weeks, but this

Re: Too many open files EAP-TLS

Jason Englander wrote: It's a EAP-TLS setup with OpenSSL verifying via 'client = ', tmpdir = /tmp/radiusd OK... Everything has been fine for weeks, but this morning: Jan 3 08:04:32 dns1 radiusd[22737]: Invalid user: [xx/no User-Password attribute] (from client port 0 cli

Re: Too many open files EAP-TLS

Alan DeKok wrote: The odd thing is that the code which writes that file does: open file write data close file It's a little hard to understand how those files are left open. Never mind... reading the man pages would be a good idea. I've pushed a fix to the git

Re: Too many open files EAP-TLS

On Mon, 3 Jan 2011, Alan DeKok wrote: Never mind... reading the man pages would be a good idea. I've pushed a fix to the git repository, branch v2.1.x. Thanks much for the speedy fix. Only one authentication thus far, but that seems to have done the trick. Jason -- Jason Englander