(RADIATOR) Splitting logfiles

[Patrick Renkens]

Hi Hugh,

What's happening is that there are no errors generated, so I cannot send 
any usefull debugging info. And there is simply no file created as 
defined in the <AuthBy GROUP> clause when the specified Handler clause 
is being used by a RADIUS-request.
Normal logging is written in the file defined by LogFile (%L/log.%Y%m%d) 
or, when I do not define Logfile, in the default file (%L/logfile).

Regards,
Patrick Renkens


Hugh Irvine wrote:
> 
> Hello Patrick -
> 
> Without a description of the problem and a trace 4 debug(s) showing  
> what is happening it is impossible to say.
> 
> regards
> 
> Hugh
> 
> 
> On 29 May 2006, at 07:30, Patrick Renkens wrote:
> 
>>
>> Hi High,
>>
>> I have tried the following which did not turn out to be the solution.
>> Any clue?
>>
>> In a main Radiator config file I have defined:
>>
>> Trace           4
>> LogDir          /data/logging
>> LogFile         %L/log.%Y%m%d (or /dev/null?)
>>
>> <AuthBy GROUP>
>>         <Log FILE>
>>                 Identifier      Log1
>>                 Filename        %L/log1.%Y%m%d
>>         </Log>
>>         <Log FILE>
>>                 Identifier      Log2
>>                 Filename        %L/log2.%Y%m%d
>>         </Log>
>> </AuthBy>
>>
>>
>> For different types of usage I have included other Radiator  
>> configfiles like:
>> include /usr/local/etc/radius-1.cfg
>> include /usr/local/etc/radius-2.cfg
>> etc.
>>
>> In these included config files I have defined handlers like:
>>
>> <Handler Client-Identifier=/^client$/>
>>         <AuthBy RADIUS>
>>                 Host                    server.subdomain.domain
>>                 Secret                  ##########
>>                 AuthPort                1812
>>                 AcctPort                1813
>>         </AuthBy>
>>         Log                             Log1
>> </Handler>
>>
>>
>> Regards,
>> Patrick Renkens
>>
>>
>>
>> Hugh Irvine wrote:
>>
>>> Hello Patrick -
>>> The trick to this is to define the <Log FILE> clauses inside an   
>>> AuthBy GROUP at the global level, then refer to them in the   
>>> corresponding Handlers.
>>> # define logs
>>> <AuthBy GROUP>
>>>         <Log FILE>
>>>         Identifier Log1
>>>         .....
>>>     </Log>
>>>     <Log FILE>
>>>         Identifier Log2
>>>         .....
>>>     </Log>
>>>     <Log FILE>
>>>         Identifier Log3
>>>         .....
>>>     </Log>
>>> </AuthBy>
>>> .....
>>> <Handler .....>
>>>     Log Log1
>>>     .....
>>> </Handler>
>>> <Handler .....>
>>>     Log Log2
>>>     .....
>>> </Handler>
>>> <Handler .....>
>>>     Log Log3
>>>     .....
>>> </Handler>
>>> .....
>>> hope that helps
>>> regards
>>> Hugh
>>> On 10 May 2006, at 23:51, Patrick Renkens wrote:
>>>
>>>> Hi all,
>>>>
>>>> I'm afraid my original question was misunderstood, or I was not   
>>>> clear enough ;-)
>>>>
>>>> What I would like to achieve is that different Handlers write  
>>>> their  log/debug-info into different logfiles, for instance with  
>>>> the <Log  File> clause?
>>>>
>>>> But for this to happen, one should also use the global  parameters  
>>>> 'LogFile %L/log.%Y%m%d' and 'Trace 4', and this means  that log/ 
>>>> debug-info is written in both the defined logfiles.
>>>>
>>>> In an ideal situation I would like to have general log/debug- info  
>>>> (starting, stopping, etc.) in a logfile defined with the  global  
>>>> LogFile-parameter, and log/debug-info for different user- groups in  
>>>> other logfiles.
>>>>
>>>> Regards,
>>>> Patrick Renkens
>>>>
>>>>
>>
>>
>>
>> -- 
>> Archive at http://www.open.com.au/archives/radiator/
>> Announcements on radiator-announce at open.com.au
>> To unsubscribe, email 'majordomo at open.com.au' with
>> 'unsubscribe radiator' in the body of the message.
> 
> 
> 


-- 




--
Archive at http://www.open.com.au/archives/radiator/
Announcements on radiator-announce at open.com.au
To unsubscribe, email 'majordomo at open.com.au' with
'unsubscribe radiator' in the body of the message.