Re: Space after exec module - is it a bug?

Lech Karol Pawłaszek wrote: Hello. I've encountered a weird problem. Tested on the newest stable (2.1.3) too. Well it's not a problem anymore since I found out a way to make my unlangish things work but: I wanted to check some things in post-auth. I am passing some arguments to my script and I

Space after exec module - is it a bug?

Hello. I've encountered a weird problem. Tested on the newest stable (2.1.3) too. Well it's not a problem anymore since I found out a way to make my unlangish things work but: I wanted to check some things in post-auth. I am passing some arguments to my script and I want to do something based on

Re: Space after exec module - is it a bug?

Lech Karol Pawłaszek wrote: Argh! True. However I still have the same symptoms even if I'll put the missing brace like this: The exec module converts all carriage returns to spaces. This is likely what's happening here. Maybe it should do that for all carriage returns *except* for the

Re: Space after exec module - is it a bug?

Phil Mayers wrote: Lech Karol Pawłaszek wrote: [...] switch %{exec:/script %{User-Name} %{outer.request:Calling-Station-Id} { You're missing a closing } I suspect this is adding a trailing to the output [...] if (%{Calling-Station-Id} == %{exec:/script2 %{Calling-Station-Id}) {