chukwa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bill Graham (JIRA)" <>
Subject [jira] Commented: (CHUKWA-446) Refactor tools/init.d scripts
Date Tue, 19 Jan 2010 22:47:54 GMT


Bill Graham commented on CHUKWA-446:

So we're talking about having the general purpose chukwa wrapper script, as well as the start-*,
stop-* scripts in bin? If so I'm also good with this refactoring. I'm particularly interested
in the start-*, stop-* scripts.

If it's at all feasible, I'd like to be able to able to have options on
to 1.) not start dbAdmin; and 2.) to not modify the crontab. We don't use dbAdmin and our
rpm install manages crontab entries. Again, a nice to have. Perhaps this is beyond the scope
of this refactor.

> Refactor tools/init.d scripts
> -----------------------------
>                 Key: CHUKWA-446
>                 URL:
>             Project: Hadoop Chukwa
>          Issue Type: Improvement
>            Reporter: Bill Graham
>            Assignee: Eric Yang
>         Attachments: chukwa
> 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.

View raw message