[
https://issues.apache.org/jira/browse/CHUKWA-446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12799369#action_12799369
]
Bill Graham commented on CHUKWA-446:
------------------------------------
I'm also fine without using the init.d scripts, since after looking more
closely at the bin/stat-*.sh scripts they seem like they'll work better for my
needs anyway.
@Eric +1 on renaming jettyCollector.sh to collector.sh for consistency and
following the foo.sh, start-foo.sh and stop-foo.sh pattern.
If we're going to refactor the start-*.sh scripts I'd like to suggest we add a
feature to slaves.sh, where if no hostnames are configured, the default
behavior would be to start the daemon on localhost without ssh'ing. This would
basically be the same as the wrapped script, just with pid files managed by
start/stop wrapper.
> 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
>
> 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.
