[ClusterLabs] Antw: Re: No Cluster fun (split brain)

Jan Friesse jfriesse at redhat.com
Wed May 20 07:24:49 EDT 2015


Ulrich Windl napsal(a):
>>>> Jan Pokorný<jpokorny at redhat.com> schrieb am 19.05.2015 um 20:38 in
> Nachricht
> <20150519183855.GK7411 at redhat.com>:
>> On 19/05/15 17:50 +0200, Ulrich Windl wrote:
>>> Now if the corosync guys would add comments to their C-code or at
>>> least would respond to inquiried to their advertised mailing list...
>> As I haven't found any posting of yours in dedicated corosync ML,
>> I suppose you are already referring to this very one per
>> "the advertisement":
> I only found the "discuss" mailing list, and I tried to subscribe, but never
> got anything since then. I also think I send a message to "discuss" a few days
> after subscribing, but still I got back nothing...

That's weird. There is really no mail from you on ML (even not in
pending for approval). Also you are really not in membership list.

So I've just tried (successfully) subscribe coro ML. Manual: Go to
http://lists.corosync.org/mailman/listinfo/discuss, put your email
address to "Your email address:" field, click subscribe. You should get
email from discuss-request at corosync.org with subject "confirm
[0-9[a-f]*". Then just click on the link in the email and you should be
subscribed. If email doesn't arrived to you, please check your spam
folder or your mail server log if message was not trowed.

Also you've wrote directly to me and I've replied you giving you two
options where to send patches. ML or github pull (so use this option if
ML doesn't work for you).

>> http://lists.corosync.org/pipermail/discuss/2015-February/003464.html 
>> FWIW, adding comments to the code after-the-fact is something highly
>> unlikely unless you want to take a part in that.  You have the
> Guessing from the code of a routine what the routine is probably meant to do
> is close to impossible, like guessing what the return codes try to say.
> To give others an impression how the typical code looks like, I pick a random
> routine from exec/coroparse.c (There really are no comments before that
> routine):
> ---snip---
> static char *strchr_rs (const char *haystack, int byte)
> {
>         const char *end_address = strchr (haystack, byte);
>         if (end_address) {
>                 end_address += 1; /* skip past { or = */
>                 end_address += strspn (end_address, " \t");
>         }
>         return ((char *) end_address);
> }
> ---

I strongly believe somebody who knows what strchr does is able to find
out quite quickly what strchr_rs does.


>> opportunity to influence the in-code verbosity within the patches
>> being posted to that list, though.
> Once I feel the list is connected, I have no problems with that.
> Regards,
> Ulrich
> _______________________________________________
> Users mailing list: Users at clusterlabs.org
> http://clusterlabs.org/mailman/listinfo/users
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org

More information about the Users mailing list