Hey Bala, I just tried to change vdsmd start prior order to 85 and it looks fine and works, but we never consider counting on it and that's why we put it as the last service to run (99) - the trivial dependencies are on network services and storage services, but we might need more services to run before starting up vdsm.. for example, sanlock is set to 97 right now and vdsmd needs to start after sanlock service.
It looks risky to change it to 85. Instead I prefer to change tuned service start prior level to 99 and vdsmd to 98 if it's possible, although we have to see if there is another service with start level 98 that vdsmd depends on.. Is it possible to change tuned start level? Regards, Yaniv. ----- Original Message ----- From: "Balamurugan Arumugam" <barum...@redhat.com> To: "VDSM Project Development" <vdsm-devel@lists.fedorahosted.org> Sent: Monday, March 11, 2013 6:39:44 PM Subject: [vdsm] priority change of vdsmd v4.9.6 Hi list, I am integrating virt and gluster tuned profile into Red Hat Storage which falls into a bug[1] which requires to change in startup of vdsmd prior to tuned service. Currently vdsmd chkconfig priority is 'chkconfig: 2345 99 00' and tuned is 'chkconfig - 86 15'. I would like to know whether changing vdsmd priority to 'chkconfig: 2345 85 00' has any side effects or not? I use vdsm v4.9.6 Thanks, Regards, Bala [1] https://bugzilla.redhat.com/show_bug.cgi?id=908884 _______________________________________________ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel _______________________________________________ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
