The logs etc, have to break out for correct locations for Linux.. etc. It might be worth doing
a wiki page that defines it for each platfrom

Carl.


Steve Vinoski wrote:
Hi Marnie,

Maybe I'm missing something, rather than being controlled only by the QPID_WORK env var, should there not also be a default for such things that reflects the underlying platform? For example, on UNIX, logs and such typically go under /var/log, and /var is also used for application-specific data.

If QPID_WORK isn't set, where do the logs and such go?

thanks,
--steve

On Oct 10, 2006, at 9:41 AM, Marnie McCormack (JIRA) wrote:

     [ http://issues.apache.org/jira/browse/QPID-30?page=all ]

Marnie McCormack resolved QPID-30.
----------------------------------

    Resolution: Fixed

Added the variable $QPID_WORK to the common/bin/qpid-run script and into the startup command line as a system property

Allow configuration of working/log directories written to by broker
-------------------------------------------------------------------

                Key: QPID-30
                URL: http://issues.apache.org/jira/browse/QPID-30
            Project: Qpid
         Issue Type: New Feature
        Environment: All
           Reporter: Marnie McCormack
        Assigned To: Marnie McCormack

At present, the working directory to which logs and persistence directories (if in use) write is setup to be under the $QPID_HOME directory. However, for many users it is not desirable that the installed location for an application is also the working directory. In a corporate environment that I have worked in, for example, the install directory is always read only as a method of release control for production environments. Thus, we need an additional environment variable $QPID_WORK which can be used for this purpose to be added to the qpid-run script. It will be defaulted to be $HOME rather than $QPID_HOME as this works better for the one example of real use that I'm aware of.

--This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira




Reply via email to