Hi, a similar issue with the config parser here... The following worked nicely in 2.1.10, but barks with "Unexpected text else" (and with the obvious change to elsif, "Unexpected text elsif"). if ( "%{NAS-Identifier}" == "ejabberd" ) { update request { RESTENA-Service-Type = "Staff-Jabber" } } else if ( "%{NAS-Identifier}" == "AAI-Staff-IdP" ) { update request { RESTENA-Service-Type = "Staff-AAI" } } else update request { RESTENA-Service-Type = "Staff-%{client:staff_type}" } But... what's wrong with that? How would I have to fix the syntax to be acceptable? Apologies for not spotting it earlier... I run 2.1.x on a test server, but the test server's config is only slightly more simple than the production one - it has no "else" in that authorize block. Stefan Winter Am 20.06.2011 16:47, schrieb Alan Buxey:
Hi,
It's been a long time since 2.1.10. We're happy to release version 2.1.11, which has many of useful new features, and a number of minor bugs fixed. yay! :-) <virtual champagne cork released>
however, a nice quirky change in config parser means that any unlang style code with an 'if' condition check that end with no space before curlies eg
if (condition){
rather than
if (condition) {
causes the daemon to not start...
quick one-line config changer on the command line is:
sed -i -e 's/){/) {/g' *
this fixed at least 45 instances of such coding ctyle in my virtual servers
alan - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
-- Stefan WINTER Ingenieur de Recherche Fondation RESTENA - Réseau Téléinformatique de l'Education Nationale et de la Recherche 6, rue Richard Coudenhove-Kalergi L-1359 Luxembourg Tel: +352 424409 1 Fax: +352 422473