[
https://issues.apache.org/jira/browse/BIGTOP-596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13396288#comment-13396288
]
Johnny Zhang edited comment on BIGTOP-596 at 6/20/12 8:09 PM:
--------------------------------------------------------------
please review BIGTOP_596-3.txt, it includes parts:
1. move the service configurations from groovy code to manifest xml
2. copy configurations inside of <config> block into the config file
3. add a new init() function in Service class, and if <init> is not empty, do
'service $svc_name init' to init service
I verified it in centos5_64 VM
was (Author: dreambird):
please review BIGTOP_596-3.txt, it includes parts:
1. move the service configurations from groovy code to manifest xml
2. copy configurations inside of <config> block into the config file
3. add a new init() function in Service class, and if <init> is not empty, do
'service $svc_name init' to init service
I verified it in centos5_32 VM
> move service configuration from groovy code to package xml manifest file
> ------------------------------------------------------------------------
>
> Key: BIGTOP-596
> URL: https://issues.apache.org/jira/browse/BIGTOP-596
> Project: Bigtop
> Issue Type: Bug
> Components: Tests
> Affects Versions: 0.4.0
> Reporter: Johnny Zhang
> Assignee: Johnny Zhang
> Fix For: 0.4.0
>
> Attachments: BIGTOP_596-2.txt, BIGTOP_596-3.txt, BIGTOP_596.txt
>
>
> the current package test doesn't format namenode, so that
> hadoop-hdfs-namenode daemon cannot be started
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
