Re: Freeradius from inetd

2005-10-09 Thread Adharsh P
Hello Alan,

Thanks, I am wondering, is there any other way that I can start
radiusd automatically after every boot.

Thanks and regards,
adharsh

 --
> > I am trying to start radiusd from inetd.conf.
>   Don't.  It won't work.
>   Alan DeKok.
--

- 
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html


Freeradius from inetd

2005-10-07 Thread Adharsh P
Hello all,

I am trying to start radiusd from inetd.conf.

The entry in inetd.conf
 radiusdgramudp  waitroot   
/usr/local/sbin/radiusd radiusd

I have added the entries in /etc/services/ as

radius 1812/udp
radacct 1813/udp

when I reload inetd, the logs say
inetd[940]: /usr/local/sbin/radiusd: exit status (1)

netstat -n  displays *1812 but not *1813
udp  120  0  *.1812*.*

however radiusd is not accepting any request from the localhost using
radclient/radtest.

However, when I run radiusd from the command line  /usr/local/sbin/radiusd
radiusd starts and accepts requests.

netstat -n displays
udp0  0  *.1812*.*
udp0  0  *.1813*.*

I am not able to understand when using inetd, radiusd doesn't start.
Am I missing something ? Do I have to modify anything in the
configuration files ? I tried looking in the docs and archives,  there
is no mention on this. Could you please guide me, or give some
pointers on where to look for.

regards,
adharsh.

- 
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html


RE: Tru64 again

2005-10-05 Thread Adharsh P
Hello Tim Winders,

When you run configure in Tru64, configure sets GETHOSTBYADDRRSTYLE
and GETHOSTBYNAMERSTYLE to GNUSTYLE in src/include/autoconf.h

Modify the two lines in src/include/autoconf.h

-#define GETHOSTBYADDRRSTYLE GNUTYPE
-#define GETHOSTBYNAMERSTYLE GNUTYPE

to

+#undef GETHOSTBYADDRRSTYLE
+#undef GETHOSTBYNAMERSTYLE

Also undef OSFC2 if you haven't already done this.

do a make and make install.

Run radiusd. It should be work.

---adharsh

RE: Tru64 again 

Tim Winders
Thu, 15 Sep 2005 08:17:25 -0700 
responding to my own
post.  I saw a message about looking at the core dump
in another thread.  So, I followed those instructions.  Here is the output
from gdb:

This GDB was configured as "alphaev67-dec-osf5.1"...
BFD: Unhandled OSF/1 core file section type 4464

BFD: Unhandled OSF/1 core file section type 528

BFD: Unhandled OSF/1 core file section type 0

BFD: Unhandled OSF/1 core file section type 7

BFD: Unhandled OSF/1 core file section type 16384

BFD: Unhandled OSF/1 core file section type 8192

BFD: Unhandled OSF/1 core file section type 0

BFD: Unhandled OSF/1 core file section type 32768

BFD: Unhandled OSF/1 core file section type 49152

BFD: Unhandled OSF/1 core file section type 49152

BFD: Unhandled OSF/1 core file section type 7

BFD: Unhandled OSF/1 core file section type 57344

BFD: Unhandled OSF/1 core file section type 49152


warning: big endian file does not match little endian target.
Core was generated by `
   '.
Program terminated with signal 1, Hangup.

warning: Couldn't find general-purpose registers in core file.


warning: Couldn't find general-purpose registers in core file.

#0  0x in ?? ()



when I did bt in gdb I got the same "#0  0x in ?? ()" response and
nothing else.

But, in reading the above, it seems a big endian v. little endian problem.
Does this help in getting freeradius to work on Tru64?

---

Tim Winders
Associate Dean of Information Technology
South Plains College
Levelland, TX 79336

Problem replying to my email?  Click the "Sign" button in the OE toolbar or,
better yet, get your own FREE Personal E-Mail Digital ID:
http://www.thawte.com/email/index.html

> -Original Message-
> From: Tim Winders [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, September 14, 2005 11:35 AM
> To: 'freeradius-users@lists.freeradius.org'
> Subject: Tru64 again
>
> I'm back at trying to get freeradius working under Tru64.
> This time using 1.0.5.
>
> I have an older cvs version working, but I can't remember
> what I did to make it work.  :-(  The working version I have
> is marked 1.1.0-pre0 built on Feb 17, 2005.
>
> First, in src/main/radiusd.c I have commented out the OSFC2
> define.  I do this because I'm not running C2, but it is
> always found and enabled, which kills the make.  Then, I run
> configure with these options:
>
> CFLAGS="-I/usr/local/ssl/include -I/usr/local/include"
> LDFLAGS="-L/usr/local/ssl/lib -L/usr/local/lib" LIBS="-lssl
> -lcrypto -lsecurity" ./configure \
> --disable-shared \
> --enable-ltdl-install=no \
> --with-openssl-includes=/usr/local/ssl/include \
> --with-openssl-libraries=/usr/local/ssl/lib \
> --without-mysql --disable-mysql
>
> radiusd seems to compile, but with many warnings.  However,
> when I run it, it immediately seg faults and dumps core.
> Unfortunately, I am not a programmer, so I don't know how to
> begin troubleshooting this and try to help get freeradius
> working under Tru64.
>
> I remember being told that none of the development team uses
> Tru64.  So, it's possible this will never work "right".  But,
> I'm willing to help out in whatever limited capacity I can,
> including CPU/shell account.
>
> Any useful suggestions are welcome.

- 
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html