Mailing-List: contact chukwa-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: chukwa-dev@hadoop.apache.org
Message-ID: <138960957.73561267721847564.JavaMail.jira@brutus.apache.org>
Date: Thu, 4 Mar 2010 16:57:27 +0000 (UTC)
From: "Eric Yang (JIRA)" <jira@apache.org>
To: chukwa-dev@hadoop.apache.org
Subject: [jira] Reopened: (CHUKWA-446) Refactor tools/init.d scripts
In-Reply-To: <412186746.187621263322194467.JavaMail.jira@brutus.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CHUKWA-446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Eric Yang reopened CHUKWA-446:
------------------------------


There is a problem with start-* scripts where chukwa command is already in chukwa-daemons.sh.

> Refactor tools/init.d scripts
> -----------------------------
>
>                 Key: CHUKWA-446
>                 URL: https://issues.apache.org/jira/browse/CHUKWA-446
>             Project: Hadoop Chukwa
>          Issue Type: Improvement
>            Reporter: Bill Graham
>            Assignee: Eric Yang
>         Attachments: chukwa, CHUKWA-446-2.patch, CHUKWA-446.patch
>
>
> 1. The scripts try to write lock files to /var/lock/subsys, which is owned by root. We should change this location to be somewhere that doesn't require root access.
> 2. The actual run command does an su to the CHUKWA_USER which also caused problems for us. It seems like it would be cleaner to not embed the su calls in the script, but instead allow the user to su when they run the script (which worked much better for us). That way everything done by the script would be done by the same user.
> 3. Each script has CHUKWA_HOME, CHUKWA_CONF_DIR and CHUKWA_USER hard coded. Hard coded defaults is ok, but the ability to override them without modifying the scripts would be ideal.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.