Re: [RADIATOR] per-clause vs global Logs

2013-12-09 Thread Garry Shtern
Hi Heikki, I'll give this a shot. Thanks. -Original Message- From: Heikki Vatiainen [mailto:h...@open.com.au] Sent: Saturday, December 07, 2013 7:23 AM To: Garry Shtern; radiator@open.com.au Subject: Re: [RADIATOR] per-clause vs global Logs On 12/05/2013 07:23 PM, Garry Shtern

Re: [RADIATOR] per-clause vs global Logs

2013-12-07 Thread Heikki Vatiainen
ailto:radiator-boun...@open.com.au] On > Behalf Of Heikki Vatiainen > Sent: Monday, November 25, 2013 8:48 AM > To: radiator@open.com.au > Subject: Re: [RADIATOR] per-clause vs global Logs > > On 11/12/2013 10:43 PM, Heikki Vatiainen wrote: > >> Global option would be possib

Re: [RADIATOR] per-clause vs global Logs

2013-12-05 Thread Garry Shtern
multiple of these parameters. Thanks. -Original Message- From: radiator-boun...@open.com.au [mailto:radiator-boun...@open.com.au] On Behalf Of Heikki Vatiainen Sent: Monday, November 25, 2013 8:48 AM To: radiator@open.com.au Subject: Re: [RADIATOR] per-clause vs global Logs On 11/12/2013 10:43

Re: [RADIATOR] per-clause vs global Logs

2013-11-26 Thread Heikki Vatiainen
On 11/15/2013 09:15 PM, Heikki Vatiainen wrote: > On 11/14/2013 11:41 PM, David Zych wrote: > >> My problem with PacketTrace as currently implemented is that it adds packet >> dumps to _every_ global logger, whereas I'd really like to control where >> they go and e.g. not send them to syslog. >>

Re: [RADIATOR] per-clause vs global Logs

2013-11-25 Thread Heikki Vatiainen
On 11/12/2013 10:43 PM, Heikki Vatiainen wrote: > Global option would be possible at least. Lets see what it would take to > have it as a per Handler option. Value for per Handler option should > probably default to the global option so it can be overridden easily. The patches now have changes th

Re: [RADIATOR] per-clause vs global Logs

2013-11-15 Thread Heikki Vatiainen
On 11/14/2013 11:41 PM, David Zych wrote: > My problem with PacketTrace as currently implemented is that it adds packet > dumps to _every_ global logger, whereas I'd really like to control where they > go and e.g. not send them to syslog. > > I suggest a new config flag for LogGeneric which tel

Re: [RADIATOR] per-clause vs global Logs

2013-11-14 Thread David Zych
On 11/12/2013, Heikki Vatiainen wrote: > On 11/12/2013 06:12 PM, David Zych wrote: >>> Now, however, I'm trying to put my Radiator servers behind a server >>> load balancer (SLB); every few seconds, the SLB sends a health check >>> request which Radiator is configured to REJECT (th

Re: [RADIATOR] per-clause vs global Logs

2013-11-12 Thread Heikki Vatiainen
On 11/12/2013 06:12 PM, David Zych wrote: >>> Now, however, I'm trying to put my Radiator servers behind a server load >>> balancer (SLB); every few seconds, the SLB sends a health check request >>> which Radiator is configured to REJECT (this is safer than ACCEPT and >>> equally effective proo

[RADIATOR] per-clause vs global Logs

2013-11-12 Thread David Zych
Heikki Vatiainen wrote: > On 11/09/2013 01:22 AM, David Zych wrote: > >> Now, however, I'm trying to put my Radiator servers behind a server load >> balancer (SLB); every few seconds, the SLB sends a health check request >> which Radiator is configured to REJECT (this is safer than ACCEPT and >

Re: [RADIATOR] per-clause vs global Logs

2013-11-11 Thread Heikki Vatiainen
On 11/09/2013 01:22 AM, David Zych wrote: > Now, however, I'm trying to put my Radiator servers behind a server load > balancer (SLB); every few seconds, the SLB sends a health check request which > Radiator is configured to REJECT (this is safer than ACCEPT and equally > effective proof that t

[RADIATOR] per-clause vs global Logs

2013-11-08 Thread David Zych
For a long time, I have used a single global and a single global , both at Trace 3, to capture everything I might want to know about that doesn't fall into the separate categories of AuthLog or AcctLogFileName. Now, however, I'm trying to put my Radiator servers behind a server load balancer (