Jan Pokorný

Also, `+` is excluded in `NCName` so it could be used instead of `%` in the above examples. I'd avoid making it to stand for `and`, since it rather algebraically...

See also a relevant discussion about an initiative to make some details rendered on the screen in some form in case of panic, which could hypothetically contain also some recent...

This part definitely needs more love: https://copr-be.cloud.fedoraproject.org/results/%40ClusterLabs/devel/epel-7-x86_64/00482520-libqb/build.log.gz ``` ==== Corrupt blackbox test 14/32 ==== [debug] shm size:8192; real_size:8192; rb->word_size:2048 [debug] read total of: 8212 ./blackbox-segfault.sh: line 17: 23805 Segmentation fault...

One of the ideas would be to add a cryptographic digest in addition to mere checksum + perhaps add `--ignore-digest` and `--ignore-checksum` switches that would allow to ignore the respective...

For posterity, Python decides to stick with [SipHash](https://131002.net/siphash/) to hash the source file for comparison against bytecode mark.

And one of stand-alone implementations thereof: https://github.com/c-util/c-siphash

Why do you close this issue then? Also, that composition is borderline impractical & inconvenient, and for said single node cluster, downright _betraying_ since the limited (and hence not applicable)...

Regarding `sync` misnomer: #239

When at it, Python offers handlers implementing also their own log rotation, based on: - size, `RotatingFileHandler`: https://hg.python.org/cpython/file/3.6/Lib/logging/handlers.py#l117 - time intervals, `TimedRotatingFileHandler`: https://hg.python.org/cpython/file/3.6/Lib/logging/handlers.py#l193 So one of the options would be...

When speaking of corosync, the risk of losing data in ``` very small time slice between copying the file and truncating it ``` is amplified by the fact that corosync...