Kostiantyn,
One more thing to clarify.
You said rebind can be avoided - what does it mean?
By that I mean that as long as you don't shutdown interface everything
will work as expected. Interface shutdown is administrator decision,
system doesn't do it automagically :)
Regards,
Honza
On Tue, Jan 20, 2015 at 11:50 AM, Jan Friesse jfrie...@redhat.com wrote:
Kostiantyn,
One more thing to clarify.
You said rebind can be avoided - what does it mean?
By that I mean that as long as you don't shutdown interface everything
will work as expected. Interface shutdown is
Got it. Thank you =)
I just thought about possibility of a NIC to burn down.
Thank you,
Kostya
On Tue, Jan 20, 2015 at 10:50 AM, Jan Friesse jfrie...@redhat.com wrote:
Kostiantyn,
One more thing to clarify.
You said rebind can be avoided - what does it mean?
By that I mean that as long
Hi,
i have a Cluster running on SLES 11 SP3. A resource group is defined. So every
entry in that resource group is a hard dependency for the folliowing resource
in that group. If just only one resource fails on both nodes, the resource
res_MyApplication won't be started. I want to change that
group grp_application res_mount-application res_Service-IP
res_mount-CIFSshareData res_mount-CIFSshareData2 res_mount-CIFSshareData3
res_MyApplication
is just a shortcut for
colocation res_Service-IP with res_mount-application
colocation res_mount-CIFSshareData with res_Service-IP
...
and
On 20 Jan 2015, at 4:13 pm, Vladislav Bogdanov bub...@hoster-ok.com wrote:
20.01.2015 02:47, Andrew Beekhof wrote:
On 17 Jan 2015, at 1:25 am, Vladislav Bogdanov
bub...@hoster-ok.com wrote:
Hi all,
Trying to reproduce problem with early stop of globally-unique
clone instances
21.01.2015 03:51, Andrew Beekhof wrote:
On 20 Jan 2015, at 4:13 pm, Vladislav Bogdanov bub...@hoster-ok.com wrote:
20.01.2015 02:47, Andrew Beekhof wrote:
On 17 Jan 2015, at 1:25 am, Vladislav Bogdanov
bub...@hoster-ok.com wrote:
Hi all,
Trying to reproduce problem with early stop of
