On Sun, Sep 4, 2016 at 10:54 AM, Yedidyah Bar David wrote:
> On Sat, Sep 3, 2016 at 1:18 PM, Gianluca Cecchi
> wrote:
> > Hello,
> > how do the two modes apply in case of single host?
> > During an upgrade phase, after having upgraded the self hosted engine and
> > leaving global maintenance and
Hi Gianluca,
I forgot to mention that you need to ensure that systemd knows that the new
file exists. You should likely run `systemctl daemon-reload` after
creating/modifying your custom systemd files. You can see that the After
directive is combined from both files. Check it out by running `sy
Il 28/Set/2016 21:09, "Gervais de Montbrun" ha
scritto:
>
> Hi Gianluca,
>
> Instead of editing the system's built in systemd configuration, you can
do the following...
>
> Create a file called /etc/systemd/system/ovirt-ha-broker.service
>
>> # My custom ovirt-ha-broker.service config that ensures
Hi Gianluca,
Instead of editing the system's built in systemd configuration, you can do the
following...
Create a file called /etc/systemd/system/ovirt-ha-broker.service
# My custom ovirt-ha-broker.service config that ensures NFS starts before
ovirt-ha-broker.service
# thanks Gervais for this
On Sun, Sep 4, 2016 at 10:54 AM, Yedidyah Bar David wrote:
> On Sat, Sep 3, 2016 at 1:18 PM, Gianluca Cecchi
> wrote:
> > Hello,
> > how do the two modes apply in case of single host?
> > During an upgrade phase, after having upgraded the self hosted engine and
> > leaving global maintenance and
On Sat, Sep 3, 2016 at 1:18 PM, Gianluca Cecchi
wrote:
> Hello,
> how do the two modes apply in case of single host?
> During an upgrade phase, after having upgraded the self hosted engine and
> leaving global maintenance and having checked all is ok, what is the correct
> mode then to put host if
6 matches
Mail list logo
