new in svn

[wlanmac]

Yes, it does. But, only from scripts that use chilli_radconfig to fetch
configurations before restarting chilli. The chilli_radconfig method is
still interesting for full configurations, but having the administrative
session update "re-configurable" settings (some settings, like
uamlisten, require chilli to be restarted) is also handy as part of
chilli's config re-read interval (this is when a new administrative-user
auth is performed to potentially update the config).



On Fri, 2009-02-13 at 09:48 +0200, Gunther Mayer wrote:
> wlanmac wrote:
> > I've made some commits to SVN. 
> >
> > The previously submitted noc2c patch was included earlier, and now I
> > have also added an option ''adminupdatefile'' ... When set, and when
> > using the Administrative-User, ChilliSpot-Config attributes returned in
> > the Admin-User Access-Accept will be written out to this
> > adminupdatefile. If the file changes, then chilli will also reread
> > configurations. So, by having a configure that includes this
> > adminupdatefile, then this way chilli can get some of it's configuration
> > via RADIUS. This will make it easier to manage some chilli config
> > options and things like uamallowed and uamdomain.
> >   
> 
> That's a very useful feature. Just as a matter of interest, how did 
> adminuser/adminpassword work before? I thought that previously it had 
> already been possible to manage chilli.conf centrally via radius?
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: chilli-unsubscribe at coova.org
> For additional commands, e-mail: chilli-help at coova.org
> Wiki: http://coova.org/wiki/index.php/CoovaChilli
> Forum: http://coova.org/phpBB3/viewforum.php?f=4
>