[
https://issues.apache.org/jira/browse/QPID-3144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13007042#comment-13007042
]
michael j. goulish commented on QPID-3144:
------------------------------------------
Fixing this in the code seems too heavy-handed.
Also, the log message that is getting in the way is presumably useful in other
contexts.
Wouldn't it be better to simply do something like the following in the affected
scripts?
my_pid=`qpidd --check | grep -v "Loaded"`
I would propose that we leave this small change out.
> qpidd --check does not work with info logging and --log-to-stdout=yes
> ---------------------------------------------------------------------
>
> Key: QPID-3144
> URL: https://issues.apache.org/jira/browse/QPID-3144
> Project: Qpid
> Issue Type: Bug
> Components: C++ Broker
> Affects Versions: 0.9
> Reporter: Alan Conway
> Assignee: Alan Conway
> Priority: Minor
> Fix For: 0.10
>
>
> qpidd --check is supposed to print the PID of a running qpidd --daemon, for
> use in scripts and the like. However with info logging and log-to-stdout
> enabled this does not work because log messages of the form:
> 2011-03-14 16:21:05 info Loaded Module: /usr/lib64/qpid/daemon/cluster.so
> precede the port number.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org
