> > ... I'm assuming this means it failed after receiving a -HUP signal?
> > (It's given one every 15 minutes to rehash our config files and usernames)
>
> Yes. It doesn't handle HUP very well.
If your userbase changes so rapidly you need to restart radius so frequently
you migh tbe better off
Justin Wheeler <[EMAIL PROTECTED]> wrote:
> ... I'm assuming this means it failed after receiving a -HUP signal?
> (It's given one every 15 minutes to rehash our config files and usernames)
Yes. It doesn't handle HUP very well.
> If so, I can deal with that, I'll just rewrite our scripts to co
After running radiusd with -xxyz -l stdout, and logging it, this was the
last output I received before it segfaulted:
Reloading configuration files.
reread_config: reading radiusd.conf
Config: including file: //etc/raddb/proxy.conf
Config: including file: //etc/raddb/clients.conf
Config: in
Mike Cathey <[EMAIL PROTECTED]> wrote:
> Thanks, I appreciate the heads up. Is it possible that my problem on
> the solaris box was the same then?
Yes. I hope to have something done soon.
Alan DeKok.
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Alan,
Thanks, I appreciate the heads up. Is it possible that my problem on
the solaris box was the same then?
I'll leave you alone so you can have more time to work on it then. =)
Have a great day!
Sincerely,
Mike
--
Mike Cathey - http://www.mikecathey.com/
Network Administrator
RTC Intern
Mike Cathey <[EMAIL PROTECTED]> wrote:
> I had a problem on the other box (linux/dual-i686) that I installed
> FreeRADIUS 0.4 on yesterday. It died with this in the log (after
> running for ~19 hours):
There's a race condition in the server that I'm in the process of
fixing. The short summa
23:01:04
SNIP
and config.log is attached.
I realized that a sig11 is normally a hardware issue, but I'm inclined
to believe that this machine is fine. Suggestions?
Cheers,
Mike
This file contains any messages produced by compilers while
running configure, to aid debuggi
