Bug 1293275 - Where to redirect Helix controller log
Where to redirect Helix controller log
Status: NEW
Product: JBoss BRMS Platform 6
Classification: JBoss
Component: Documentation (Show other bugs)
6.2.0
Unspecified Unspecified
unspecified Severity medium
: ---
: ---
Assigned To: brms-docs@redhat.com
Lukáš Petrovický
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-12-21 04:41 EST by Toshiya Kobayashi
Modified: 2016-01-08 17:17 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Toshiya Kobayashi 2015-12-21 04:41:04 EST
Document URL: 

https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_BRMS/6.2/html/Installation_Guide/Generic_Bundle_Clustering_Setup.html

Section Number and Name: 

5.2.1. Setting up a Cluster

Describe the issue: 

Example 5.7. Starting the Helix controller
===========
./run-helix-controller.sh --zkSvr server1:2181,server2:2181,server3:2181 --cluster brms-cluster 2>&1 > /tmp/controller.log &
===========

"/tmp" directory could be cleaned up by OS automatically so it's not a desired place from production perspective.

Suggestions for improvement: 

===========
./run-helix-controller.sh --zkSvr server1:2181,server2:2181,server3:2181 --cluster brms-cluster 2>&1 > ./controller.log &
===========

Note You need to log in before you can comment on or make changes to this bug.