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 (Created) (JIRA)" <ji...@apache.org> on 2012/02/23 20:32:48 UTC
[jira] [Created] (BIGTOP-416) run levels for init.d scripts need to
be harmonized
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
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
[jira] [Commented] (BIGTOP-416) run levels for init.d scripts need
to be harmonized
Posted by "Roman Shaposhnik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BIGTOP-416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13281966#comment-13281966 ]
Roman Shaposhnik commented on BIGTOP-416:
-----------------------------------------
Thanks for the review. Makes perfect sense -- updated the call as you suggested.
> 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
>
> Attachments: BIGTOP-416.patch.txt
>
>
> 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
[jira] [Updated] (BIGTOP-416) run levels for init.d scripts need to
be harmonized
Posted by "Roman Shaposhnik (Updated) (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Updated] (BIGTOP-416) run levels for init.d scripts need to
be harmonized
Posted by "Roman Shaposhnik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BIGTOP-416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Roman Shaposhnik updated BIGTOP-416:
------------------------------------
Attachment: BIGTOP-416.patch.txt
> 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
>
> Attachments: BIGTOP-416.patch.txt
>
>
> 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
[jira] [Commented] (BIGTOP-416) run levels for init.d scripts need
to be harmonized
Posted by "Bruno Mahé (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BIGTOP-416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13281755#comment-13281755 ]
Bruno Mahé commented on BIGTOP-416:
-----------------------------------
Nitpick: In the spec file, I would have spread the command on multiple lines
+1
> 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
>
> Attachments: BIGTOP-416.patch.txt
>
>
> 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