[
https://issues.apache.org/activemq/browse/AMQ-2453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=62506#action_62506
]
Marc Schöchlin commented on AMQ-2453:
-------------------------------------
Sorry, i don't own a aix system :-)
Probably its enough to modify the sheebang like this:
----
$ svn diff
Index: activemq
===================================================================
--- activemq (Revision 1021620)
+++ activemq (Arbeitskopie)
@@ -1,4 +1,4 @@
-#!/bin/bash
+#!/usr/bin/env bash
# ------------------------------------------------------------------------
# Licensed to the Apache Software Foundation (ASF) under one or more
# contributor license agreements. See the NOTICE file distributed with
----
Bash emulation of /bin/sh is often not completely compatible to the "sh" of
legacy unix systems - but most
of these systems provide the bash shell. Can you sent me the following
information:
- stdout/stderr output of a script feature which is not working using "/bin/sh
activemq"
- stdout/stderr output of a script feature which is not working with "/bin/sh
-x activemq"
> start/control-script is not suitable for professional environments
> ------------------------------------------------------------------
>
> Key: AMQ-2453
> URL: https://issues.apache.org/activemq/browse/AMQ-2453
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.3.0
> Reporter: Marc Schöchlin
> Assignee: Dejan Bosanac
> Fix For: 5.4.0
>
> Attachments: activemq, usage-example.txt
>
>
> The start-scripts "activemq" and "activemq-admin" do not seem to be ready for
> production use.
> Reasons:
> - Server does not run in background
> => this can be done by redirecting output to a file and run in background
> => in my opinion this should be implemented directly in java
> => the console log should be written by log4j to
> <install-root>/data/console.log
> - The process should be started on a non-root user
> => use 'su -c "$COMMAND" - $RUN_AS_USER'
> => this should be defined in /etc/activemq.conf
> - The script should support a "reload" feature to reload the configurartion
> (if activemq supports reloading)
> - The script should support a "status" option
> => this should show a quick overview about the state of activemq
> => this should return a value != 0 if the service is not working
> (this is important for cluster integration)
> Does anybody already working on these items?
> Do you have suggestions for a implementation?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
