On Mon, Oct 10, 2011 at 19:41, Sage Weil <[email protected]> wrote: >> >> The insserv thing is easy to workaround; just don't enable service ceph when >> installing the package :-) > > Hmm, yeah... Is that the right thing to do though? Don't RPMs normally > enable the serve when you install them?
I think it is up to the package developer. For example on CentOS 5.4 lighttpd and httpd do not start themselves, but I know the MySQL Community packages do start themselves. I know with MySQL I also always wind up immediately stopping it after it's installed to do configuration. As configuration of any given Ceph node is likely to be part of a larger configuration management/automation system it seems like it would be fine to push responsibility of "service ceph start" off onto the system administrators. I would still configure it to start automatically on boot in the rpm. Kelly -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
