[
https://issues.apache.org/jira/browse/QPID-2666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kim van der Riet resolved QPID-2666.
------------------------------------
Resolution: Fixed
Simple fix: add a '-' into the runuser statement that starts the "qpidd
--check"; this ensures that it runs in its own home directory for which it has
permissions to write.
Fixed in r.953687
> [C++ broker linux] Service init script does not handle config file with
> "log-to-file" and a relative path
> ---------------------------------------------------------------------------------------------------------
>
> Key: QPID-2666
> URL: https://issues.apache.org/jira/browse/QPID-2666
> Project: Qpid
> Issue Type: Bug
> Components: C++ Broker
> Environment: Linux
> Reporter: Kim van der Riet
> Assignee: Kim van der Riet
>
> The service start script for linux (located in qpid/cpp/etc in svn) when
> installed will fail if the "log-to-file" option is set in the qpidd.conf file
> with a relative path (eg log-to-file=my-log.txt); however an absolute path
> works ok.
> If a relative path is used, the script's use of "qpidd --check" to obtain the
> PID of the newly started qpid daemon will fail (as it will attempt to open a
> log file in a directory for which it does not have permissions); hence the
> pid file will be empty. An error message is printed, but the daemon starts
> ok. However, the missing PID means that attempting to stop the service will
> fail, and an administrator will have to find and stop the process manually.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
