(RADIATOR) not running from inetd - help!

[Tony Bunce]

Why don't you just use the rc.local method?

It works great for us and radiator wouldn't have to start for each
individual request

Thanks,
Tony B, CCNA, Network+
Systems Administration
GO Concepts, Inc. / www.go-concepts.com
Are you on the GO yet?
What about those you know, are they on the GO?
513.934.2800
1.888.ON.GO.YET


-----Original Message-----
From: Shon Stephens [mailto:sstephens at corp.goamerica.net] 
Sent: Tuesday, June 18, 2002 4:29 PM
To: 'hugh at open.com.au'; 'radiator at open.com.au'
Subject: RE: (RADIATOR) not running from inetd - help!

i changed the inetd.conf file entry to the following:

radius  dgram   udp     wait    root    /usr/local/radius/bin/radiusd
-config_file=/usr/local/radius/conf/radius.conf -foreground   #OSRadius

and i still get this in /var/adm/messages. (no logs generated by
radiator)

Jun 18 16:31:06 ny-www-03 inetd[173]: [ID 842545 daemon.warning]
/usr/local/radius/bin/radiusd: Signal 96

could this be a bug? i doubt it, but if i start radiator from any other
method, it functions properly.

thanks,
shon

-----Original Message-----
From: Hugh Irvine [mailto:hugh at open.com.au]
Sent: Monday, June 17, 2002 9:18 PM
To: Shon Stephens; 'radiator at open.com.au'
Subject: Re: (RADIATOR) not running from inetd - help!



Hello Shon -

There is no "=" for the -config_file parameter - it should look like
this:


radius  dgram   udp     wait    root    /usr/local/radius/bin/radiusd
-config_file usr/local/radius/conf/radius.conf -foreground 

BTW - we normally recommend that you start radiusd from your system
startup 
sequence (rc.local or your moral equivalent) and that you use the 
restartWrapper program included in the "goodies" directory.

regards

Hugh


On Tue, 18 Jun 2002 06:10, Shon Stephens wrote:
> ok. i have corrected some errors in my radius.conf, and in my
> /etc/inetd.conf file. here is background
>
> radiator 3.1
> solaris 8
> /usr/local/radius/bin/radiusd - location of radiusd
> /usr/local/radius/conf/radius.conf - location of radius.conf
> /usr/local/radius/conf/dictionary - location of radiator dictionary
file
>
> /etc/inetd.conf line:
> radius  dgram   udp     wait    root    /usr/local/radius/bin/radiusd
> -config_file=/usr/local/radius/conf/radius.conf -foreground
>
> an auth request is sent to my radius server. the request times out.
radiusd
> does not create any log files or log messages to stdout. however, in
the
> messages file, i now see this:
>
> Jun 17 16:10:13 ny-www-03 inetd[173]: [ID 842545 daemon.warning]
> /usr/local/radius/bin/radiusd: Signal 96
>
> does anyone know what signal 96 is?
>
> thanks,
> shon
> ===
> Archive at http://www.open.com.au/archives/radiator/
> Announcements on radiator-announce at open.com.au
> To unsubscribe, email 'majordomo at open.com.au' with
> 'unsubscribe radiator' in the body of the message.

-- 
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. Available on *NIX, *BSD, Windows 95/98/2000, NT, MacOS X.
-
Nets: internetwork inventory and management - graphical, extensible,
flexible with hardware, software, platform and database independence.
===
Archive at http://www.open.com.au/archives/radiator/
Announcements on radiator-announce at open.com.au
To unsubscribe, email 'majordomo at open.com.au' with
'unsubscribe radiator' in the body of the message.

===
Archive at http://www.open.com.au/archives/radiator/
Announcements on radiator-announce at open.com.au
To unsubscribe, email 'majordomo at open.com.au' with
'unsubscribe radiator' in the body of the message.