You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bigtop.apache.org by "Roman Shaposhnik (Updated) (JIRA)" <ji...@apache.org> on 2012/03/06 17:57:03 UTC
[jira] [Updated] (BIGTOP-416) run levels for init.d scripts need to
be harmonized
[ https://issues.apache.org/jira/browse/BIGTOP-416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Roman Shaposhnik updated BIGTOP-416:
------------------------------------
Priority: Blocker (was: Major)
> run levels for init.d scripts need to be harmonized
> ---------------------------------------------------
>
> Key: BIGTOP-416
> URL: https://issues.apache.org/jira/browse/BIGTOP-416
> Project: Bigtop
> Issue Type: Bug
> Components: General
> Affects Versions: 0.4.0
> Reporter: Roman Shaposhnik
> Assignee: Roman Shaposhnik
> Priority: Blocker
> Fix For: 0.4.0
>
>
> We have a mixture of different run levels specified for our init.d scripts. What complicates the situation is that Debian/Ubuntu don't distinguish between run levels of 2-5 at all, while all RPM-based distros seem to treat run-level 2 as a networkless one. Strictly speaking we should disable all Bigtop services when network is disabled.
> The proposal here is to set these valued in the template (init.d.tmpl) based on the type of the distro where the build is executed.
--
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