You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mesos.apache.org by "Jason Dusek (JIRA)" <ji...@apache.org> on 2014/03/17 20:03:44 UTC
[jira] [Commented] (MESOS-1103) Init.d scripts for Ubuntu
[ https://issues.apache.org/jira/browse/MESOS-1103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13938213#comment-13938213 ]
Jason Dusek commented on MESOS-1103:
------------------------------------
Try running `initctl reload-configuration`. We should probably make that a post-install task.
> Init.d scripts for Ubuntu
> -------------------------
>
> Key: MESOS-1103
> URL: https://issues.apache.org/jira/browse/MESOS-1103
> Project: Mesos
> Issue Type: Improvement
> Components: general
> Affects Versions: 0.17.0
> Environment: ubuntu 12.04
> Reporter: alexander j. perez tchernov
> Priority: Minor
> Labels: easyfix
> Attachments: mysql
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> I have installed the development release candidate http://downloads.mesosphere.io/master/ubuntu/12.04/mesos_0.18.0-rc3_amd64.deb on Ubuntu 12.04. Both startup /etc/init/mesos-master.conf and /etc/init/mesos-slave.conf scripts are optimized for Upstart Jobs.
> But I'm not sure why they don't appear in normal manual
> 'service mesos-master' invocation, so "doesn't found mesos-master job" appears regardless the fact that something is placed in /etc/init/
> This problem goes to resolved if copy the standard (e.g. mysql) init.d-to-upstart wrapper to /etc/init.d/mesos-master and /etc/init.d/mesos-slave
--
This message was sent by Atlassian JIRA
(v6.2#6252)