You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mesos.apache.org by "alexander j. perez tchernov (JIRA)" <ji...@apache.org> on 2014/03/15 15:51:42 UTC
[jira] [Created] (MESOS-1103) Init.d scripts for Ubuntu
alexander j. perez tchernov created MESOS-1103:
--------------------------------------------------
Summary: 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
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, and doesn't found mesos-master regardless the fact that something is placed in /etc/init/
This problem is resolved if copy the standard (e.g. mysql) init.d-to-upstart wrapper to /etc/init.d/mesos-master /etc/init.d/mesos-slave
--
This message was sent by Atlassian JIRA
(v6.2#6252)