Re: ceph.conf changes and restarting ceph.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I think this is not quite right now:

"Upstart does not require you to define daemon instances in the Ceph configuration file (*although, they are still required for sysvinit should you choose to use it*)."

I find that simply doing:

$ mv upstart sysvinit

in the various mon/osd/mds etc dirs results in a config that allow sysv init to start and stop all the various daemons without any specific mention in ceph.conf. I'm using Ubuntu 13.04 and 13.10.

Regards

Mark

On 25/09/13 05:32, John Wilkins wrote:
Either one should work. For RHEL, CentOS, etc., use sysvinit.

I rewrote the ops doc, but it's in a wip branch right now. Here:
http://ceph.com/docs/wip-doc-quickstart/rados/operations/operating/

I still may make some edits to it, but follow the sysvinit section.



_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com




[Index of Archives]     [Information on CEPH]     [Linux Filesystem Development]     [Ceph Development]     [Ceph Large]     [Ceph Dev]     [Linux USB Development]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [xfs]


  Powered by Linux