Thanks for interesting info, John. Seems that I must be ashamed for inaccurate
statements.
I'm trying to configure FreeRadius to use MOTP-AS, which is a set of PHP
scripts and SQL database.
I haven't spoke of unix enviroment, I've spoke about this, FreeRadius run-time
variables. Or, if more precisely, about %{Packet-Src-IP-Address}. This variable
presented in /var/log/radius/radius.log, which apparently has been accepted for
apache log. There %{Packet-Src-IP-Address} variable requested by
/var/www/html/radius-client.php script (this script takes clients IP and
searches for this client secret word in sql database), but this script works as
I demonstrated in my last post.
So, can %{Packet-Src-IP-Address} be handled differently in "debug" and
"service" modes and cause problems in FreeRADIUS work?
17.08.2012, 16:49, "John Dennis" <jden...@redhat.com>:
> On 08/17/2012 04:23 AM, Бедняков Алексей wrote:
>> Maybe FreeRADIUS enviroment variables work different in debugging and
>> service modes? Or I miss something else?
> Well, I'm not too sure what your actually doing because what you posted
> appears to be an apache log but to answer your question concerning
> environment variables, yes of course the handling of environment
> variables are different when run from init. Generally whatever launches
> daemons (there are different mechanisms) will not pass environment
> variables to the daemon. This is for security reasons. If memory serves
> me correctly there are a handful of special environment variables that
> do get passed, but in general the answer is system daemons with root
> privileges execute in a clean environment.
>
> John
>
> --
> John Dennis <jden...@redhat.com>
>
> Looking to carve out IT costs?
> www.redhat.com/carveoutcosts/
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
