> > To: "users"
> > Sent: Wednesday, January 20, 2016 12:21:41 PM
> > Subject: Re: Setting log level on running broker
> >
> > That looks perfect (and much more aesthetically pleasing than my
> version).
> > Can we have an official release soon?
>
On 01/20/2016 09:39 PM, Chuck Rolke wrote:
Alan's commit db7b30e was released in qpid-cpp-0.34 July, 2015.
That didn't include the tools though, I don't think.
-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For a
sday, January 20, 2016 12:21:41 PM
> Subject: Re: Setting log level on running broker
>
> That looks perfect (and much more aesthetically pleasing than my version).
> Can we have an official release soon?
>
> On 20 January 2016 at 17:12, Gordon Sim wrote:
>
> >
That looks perfect (and much more aesthetically pleasing than my version).
Can we have an official release soon?
On 20 January 2016 at 17:12, Gordon Sim wrote:
> On 01/20/2016 05:05 PM, Chris Richardson wrote:
>
>> Hi,
>>
>> It would be really nice to have a command-line method for setting the
>
On 01/20/2016 05:05 PM, Chris Richardson wrote:
Hi,
It would be really nice to have a command-line method for setting the
log level on a running broker (c++), as discussed here:
http://grokbase.com/t/qpid/users/11bxbmbxq3/set-log-level
The suggested solution with qpid-ctrl tool does work, but s
Hi,
It would be really nice to have a command-line method for setting the log
level on a running broker (c++), as discussed here:
http://grokbase.com/t/qpid/users/11bxbmbxq3/set-log-level
The suggested solution with qpid-ctrl tool does work, but since this is, as
mentioned in the article, a test