Re: Re: Raadrelay and coredumps..
Terry J Fike Jr schrieb: Okay, quick (and possible moot) question... could there be issues on this because of compiling it 64bit instead of 32 bit? Actually what for? You do realize that there are a couple of _dis_advantages of building 64bit stuff (larger executables, more memory consumption, possibly slightly slower)? While there are big advantages for certain applications (e.g. databases), I don't see the point of doing that for a RADIUS server... Regards, Stefan - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Re: Raadrelay and coredumps...
*sigh* okay, first off, shoot me...i didn't read /doc/bugs right and i hadn't recompiled with the --enable-developer so, i did that...same output from the core (Couldn't find general-purpose registers in core file) recompiled it a couple times... once with just --disable-shared still cores... once with --enable-developer (without --disable-shared) still cores, no change in output inside gdb once with --enable-developer with --disable-shared still cores, no change in output inside gdb one thing though, while in the make process with --enable-developer i received lots of warnings (mostly from md4.c) but no errors. is this normal when compiling with --enable-developer? also...any other ideas? -- Terry J Fike Jr System Administrator MTA Solutions 907-793-4100 [EMAIL PROTECTED] - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Re: Raadrelay and coredumps...
Terry J Fike Jr [EMAIL PROTECTED] wrote: so, i did that...same output from the core (Couldn't find general-purpose registers in core file) That's very strange. once with just --disable-shared still cores... Did you do that after deleting *all* files installed by the server? If one of your previous builds is broken, then any new build MAY end up using that. You MUST start from a clean system in order to verify that the new build is OK. I haven't seen any similar problems with Solaris. I suggest trying with a different Solaris box. one thing though, while in the make process with --enable-developer i received lots of warnings (mostly from md4.c) but no errors. is this normal when compiling with --enable-developer? Yes. Developers want to see more warnings than others. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Re: Re: Raadrelay and coredumps...
I did amake distclean before ./configure each time and i ran the radrelay from inside src/main (i didn't do make install on any of these runs) with the exception of the radiusd.conf file, i've been using pretty much the same config files since 0.8.3 (though i think i changed to the new clients.conf in 1.0.0 and copied that into 1.0.2) the radiusd.conf i edit from scratch with each new version based on the conf file from the previous version. unfortunetly, i'm doing this in a production environment, so swapping servers isn't going to be easy, but i'll see what i can do. (i have a lot of things :( tied into the same ip as radius) -- Terry J Fike Jr System Administrator MTA Solutions 907-793-4100 [EMAIL PROTECTED] - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Re: Raadrelay and coredumps...
Terry J Fike Jr [EMAIL PROTECTED] wrote: I did amake distclean before ./configure each time The *installed* files may be causing problems. and i ran the radrelay from inside src/main (i didn't do make install on any of these runs) Hmm... I can't recall any issues with radrelay. with the exception of the radiusd.conf file, i've been using pretty much the same config files since 0.8.3 (though i think i changed to the new clients.conf in 1.0.0 and copied that into 1.0.2) That shouldn't be a problem. radrelay doesn't read most of the configuration files. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Re: Re: Raadrelay and coredumps...
Terry J Fike Jr [EMAIL PROTECTED] wrote: I did amake distclean before ./configure each time The *installed* files may be causing problems. even if i'm telling a different prefix each time? (i ask because i have 1.0.2 in /usr/local and 1.0.0 in /opt) as i make new versions i just change the prefix so i can leave the old version running. 1.0.0-pre3 used to be in /usr/local but i deleted all those files before compiling 1.0.2 -- Terry J Fike Jr System Administrator MTA Solutions 907-793-4100 [EMAIL PROTECTED] - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Re: Raadrelay and coredumps..
Terry J Fike Jr [EMAIL PROTECTED] wrote: could there be issues on this because of compiling it 64bit instead of 32 bit? Most of my older versions were 32 bit, but since getting oracle installed 64 bit finally, i installed the newer (1.0.0 and 1.0.2) 64bit? That certainly could be the cause. If you have 32-bit 64-bit FreeRADIUS modules on the same machine, there will most likely be problems. Ensure that only ONE kind of module is on the machine, anywhere. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Re: Raadrelay and coredumps...
Terry J Fike Jr [EMAIL PROTECTED] wrote: The *installed* files may be causing problems. even if i'm telling a different prefix each time? Yes. If the dynamic linker knows to find the modules under one prefix, it may find those modules when building another version of the server on the same machine. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
