On Tue, Nov 19, 2013 at 03:21:41PM +0100, Lars Marowsky-Bree wrote:
> The goal here is that we know the other endpoint is down (we received a
> node down event and have completed fencing at that stage). Hence,
> SO_LINGER to speed up the shutdown of the socket seems appropriate.
Should your patch
(I sent this before, but the mail wasn't going through. Trying again.
Sorry for a possible duplicate.)
On 2013-11-13T12:24:49, David Teigland wrote:
> There are significant subtleties involved in using SO_LINGER with tcp.
> I do not know whether applying it here would be good or bad in the tcp
>
On Tue, Nov 19, 2013 at 11:06 AM, Gianluca Cecchi wrote:
> Is this expected behaviour? Any way to configure to try to restart in
> place the resource without manual intervention when a resource is
> configured as non critical?
>
> Thanks in advance,
> Gianluca
BTW: I did read inside the manual t
Hello,
I have a cluster with RH EL 6.3
cman-3.0.12.1-32.el6_3.2.x86_64
rgmanager-3.0.12.1-12.el6.x86_64
I configure ssh in cluster changing the default init script.
Then I configure it as a non critical resource in a service section
...
...
. . .
