Segfault after HUP
Hello, I'm running a freeradius server on a fresh slackware 11 installation. Everything seems to work OK, except after i've done a 'killall -HUP radiusd'. The server reloads it's configurationfiles, but once the first request comes in after this, it segfaults. I'm using the standard config whit the exception of an added fast_users module, which is also the onlyone I use for authentication. I currently have only one user in the users_fast file. Is this a known problem? What can I do to fix this? If you need more info, do ask. -Bastiaan
Bastiaan van Kesteren wrote:
I'm running a freeradius server on a fresh slackware 11 installation. Everything seems to work OK, except after i've done a 'killall -HUP radiusd'. The server reloads it's configurationfiles, but once the first request comes in after this, it segfaults.
Yes. It doesn't handle HUP well.
Is this a known problem? What can I do to fix this? If you need more info, do ask.
The fix, unfortunately, is either don't HUP, or fairly large code changes to support HUP. 2.0 will deal with HUP a fair bit better. Not perfectly, but it should no longer crash. Alan DeKok. -- http://deployingradius.com - The web site of the book http://deployingradius.com/blog/ - The blog
participants (2)
-
Alan DeKok -
Bastiaan van Kesteren