Hi Christine,

> https://github.com/corosync/corosync/commit/53f67a2a7914228f1a406aad61ea6768525e11b0


I confirmed that your correction was right.


I wish an original problem is solved by future improvement.


Many Thanks!
Hidoe Yamauchi.


----- Original Message -----
> From: "[email protected]" <[email protected]>
> To: "[email protected]" <[email protected]>
> Cc: 
> Date: 2015/4/18, Sat 00:09
> Subject: Re: [corosync] It is sometimes judged to be node trouble.
> 
> Hi Christine,
> 
>> 
> https://github.com/corosync/corosync/commit/53f67a2a7914228f1a406aad61ea6768525e11b0
> 
> 
> Thank you for a patch
> I will really confirm the log of the patch next week.
> 
> Best Regards,
> Hideo Yamauchi.
> 
> 
> ----- Original Message -----
>>  From: Christine Caulfield <[email protected]>
>>  To: [email protected]
>>  Cc: 
>>  Date: 2015/4/17, Fri 23:52
>>  Subject: Re: [corosync] It is sometimes judged to be node trouble.
>> 
>>  On 17/04/15 15:40, [email protected] wrote:
>>>   Hi Christine,
>>> 
>>> 
>>>>>   Surely log will be to help a system-manager.
>>>>>     * The system-manager can suppose that it may be a cause of 
>>  "A 
>>>>   Processor failed..." that at least LEAVE was thrown away.
>>>>>    
>>>>    
>>>>   Agreed, I have posted a patch below
>>> 
>>> 
>>>   All right.
>>>   I look forward to your patch.
>>> 
>>> 
>> 
>> 
>> 
> https://github.com/corosync/corosync/commit/53f67a2a7914228f1a406aad61ea6768525e11b0
>> 
>> 
>> 
>> 
>>  Chrissie
>>  _______________________________________________
>>  discuss mailing list
>>  [email protected]
>>  http://lists.corosync.org/mailman/listinfo/discuss
>> 
> 
> _______________________________________________
> discuss mailing list
> [email protected]
> http://lists.corosync.org/mailman/listinfo/discuss
> 

_______________________________________________
discuss mailing list
[email protected]
http://lists.corosync.org/mailman/listinfo/discuss

Reply via email to