Hello list. I have looked all over google for a solution to this but
have yet been unable to find one that doesn't include "downgrade gcc
to 4.1" which is not an option for me right now. If anyone can help
I'd be greatly appreciative.
I am trying to build qpidc-0.12 on a backtrack 5 R1 image but
On 09/12/2011 06:05 AM, Pavel Moravec wrote:
Hello,
is there a list of areas we can modify logging level in cpp broker? I mean, when using
"--log-enable debug:framing" option, list of verbosity levels is printed in
qpidd help. But I can't find anywhere the list of areas to debug.
(I suppose th
On 09/09/2011 01:11 PM, Alex Kulyavtsev wrote:
On Sep 9, 2011, at 11:27 AM, Fraser Adams wrote:
It seems a very reasonable requirement to be able to provision
administratively created queues/exchanges/bindings/links etc. via broker
startup config.
Yes, it is desirable feature, especially for
On 09/09/2011 05:11 AM, Jakub Scholz wrote:
Just an update to this - there seems to be a bug in the cman /
corosync. When they are run together, the corosync doesn't seem to
read the uidgid.d settings. Therefore if you want to use cman and
corosync, you have to run the broker as root. That is not
Hello,
is there a list of areas we can modify logging level in cpp broker? I mean,
when using "--log-enable debug:framing" option, list of verbosity levels is
printed in qpidd help. But I can't find anywhere the list of areas to debug.
(I suppose the list is list of directories in qpid source, i
Hi,
same here - the .pm does not find its way using the "install" target in
0.10.
Is there a patch-less way to tell "configure" to place the perl
libraries to another location than {prefix}/lib?
Best,
Cajus
On Fri, 15 Jul 2011 22:35:05 -0700 (PDT), fadams wrote:
Hi all,
I meant to say bef
