From: James Page <james.page@ubuntu.com>
To: Dan Mick <dan.mick@inktank.com>
Cc: Mike Dawson <mdawson@gammacode.com>, ceph-devel@vger.kernel.org
Subject: Re: 0.55 init script Issue?
Date: Wed, 05 Dec 2012 20:17:41 +0000 [thread overview]
Message-ID: <50BFABE5.1020904@ubuntu.com> (raw)
In-Reply-To: <50BFA354.7040308@inktank.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 05/12/12 19:41, Dan Mick wrote:
> The story as best I know it is that we're trying to transition to
> and use upstart where possible, but that the upstart config does
> not (yet?) try to do what the init.d config did. That is, it
> doesn't support options to the one script, but rather separates
> daemons into separate services, and does not reach out to remote
> machines to start daemons, etc.
>
> The intent is that init.d/ceph is left for non-Upstart distros,
> AFAICT.
>
> Tv had some design notes here:
>
> http://www.mail-archive.com/ceph-devel@vger.kernel.org/msg09314.html
>
> We need better documentation/rationale here at least.
Maybe it might be better if the ceph init script and the ceph upstart
configuration did not namespace clash; how about shifting the name of
the ceph upstart configuration to ceph-all?
- --
James Page
Ubuntu Core Developer
Debian Maintainer
james.page@ubuntu.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with undefined - http://www.enigmail.net/
iQIcBAEBCAAGBQJQv6vlAAoJEL/srsug59jDFO8P/jtC9TFAWLuFJoS/RC5nEwdO
x4OEdwYbRgE6ac5GK8ufMuqfonOVzDZ0jGxWzDrLSPQ3Ekow+E3wZFSgQN1ujhDT
0QeuAqseyMO++3Foe3HlcSAtp2IGr1VkgyLVNrnkn+rK/C8UOQnISeCvT30WFTEJ
xpr+DSiv2ZjH6fogb+p+fK7lD9anywR92pM65jNpPRnMaBZ49Rjbz8Xf3+yw8EHH
DkOvFjPnIw8pWc0FPfgbFOZNksOQ+UoIhsJJ2I5fVfLhsdcNjC+ETePi0W4VU7mL
FZLaUlGxgeDLCvgjXZ8fQ9T0sNJuYQ7H/4A0uLWnf3uNVMsE5MLff4msgAuotxle
l6w0lC+GzlHiRe6XRMgHwKq/Ifs/oZPgdGh5V6+zOERrZrl1+Z1EiD2MQkVzxk/M
7+06V/GlKLfv/hqrGOr1JtFI3AY+p+DJttq4+UN5HmxIFeaS19rSJxBxc7TqliH9
SiaoyhC6IBm8duEYHyuHfjnVksMNA/SOD4xyxGj/KLAS9IwvQhvOnaHfpQgMR7Bl
6zRyE+kisT3aC1UyvRiWCAg+8TzhQN46oMpE1JZQTJsbW2dtdXI/Jl8vDk+I8hX2
Qola8AzSHc80tp3p51PN+83V3iqHKvXeK8G36FnJm+tKufDPVe3WnE9ig5emRDez
it86WnE+jBLtA8QlZRm8
=XIJq
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2012-12-05 20:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-05 16:15 0.55 init script Issue? Mike Dawson
2012-12-05 17:19 ` Franck Marchand
2012-12-05 18:04 ` James Page
2012-12-05 19:41 ` Dan Mick
2012-12-05 19:57 ` David Zafman
2012-12-05 20:17 ` James Page [this message]
2012-12-05 20:39 ` Gregory Farnum
2012-12-06 0:11 ` Sage Weil
2012-12-06 1:34 ` Matthew Via
2012-12-06 13:28 ` Sage Weil
2012-12-06 13:35 ` Sage Weil
2012-12-07 21:38 ` Dan Mick
2012-12-10 9:13 ` James Page
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=50BFABE5.1020904@ubuntu.com \
--to=james.page@ubuntu.com \
--cc=ceph-devel@vger.kernel.org \
--cc=dan.mick@inktank.com \
--cc=mdawson@gammacode.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.