-i and -p commandline options

[Holger Steppke]

Hi,

in the man page i found the comment that this options are deprecated
and listen/bind should be used.

Just my sentence on this why to let them stay in the code :)
I found such options very usfully maintaining same configuration across
multiple redundand servers.
So eg. Radiusd.conf could be the same (pushed from a central storage) where
the commanline option
will be adjusted per server to the ip the servers has.



Regards
Holger


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

Re: -i and -p commandline options

[Craig Huckabee]

Holger Steppke wrote:
Hi,
in the man page i found the comment that this options are deprecated
and listen/bind should be used.
Just my sentence on this why to let them stay in the code :)
I found such options very usfully maintaining same configuration across
multiple redundand servers.
So eg. Radiusd.conf could be the same (pushed from a central storage) where
the commanline option
will be adjusted per server to the ip the servers has.

Regards
Holger
Holger,
  We had this same problem - our fix was to dynamically generate the 
'listen' statements needed on each server during startup and put them in 
a file in /tmp.

  Then our central radiusd.conf uses the 'include' directive to pull in 
that file.

  --Craig
--
/ Craig Huckabee|  e-mail: [EMAIL PROTECTED] /
/ Code 715-CH   |   phone: (843) 218 5653   /
/ SPAWAR Systems Center | close proximity: Hey You!   /
/ Charleston, SC|ICBM:  32.78N, 79.93W  /
- 
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html

Re: -i and -p commandline options

[Alan DeKok]

Holger Steppke [EMAIL PROTECTED] wrote:
 I found such options very usfully maintaining same configuration across
 multiple redundand servers.

  I agree.  But until the code gets updated to make them work
properly, they won't work.

  Alan DeKok.

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