crm writes info messages into error out about crmsh HOT 4 CLOSED

All messages (or all severities) are going to stderr. That's
deliberately so.

Why would you want (or expect) INFO messages at stdout?

from crmsh.

Not all messages are error messages, some are informational. By pushing them all to stderr it becomes harder to differentiate error and non-error output. It also makes it harder to filter output since you can't redirect non-error output to somewhere else (/dev/null for example).

Is there a technical reason to put them all in stderr or is it just a matter of preference?

from crmsh.

There's no purely technical reason. I'd just expect all
messages to be sent to stderr, regardless of the severity. I'm
not aware of any convention about sending messages depending on
severity to stdout. I believe that all unix programs, at least
those I had a chance to work with, send messages to stderr, so
that they don't interfere with possible further processing in
pipes.

Otherwise, you should test for exit codes if you want to check
whether there was an error. The exit code is the ultimate result,
messages shouldn't be relied on for that.

Must say that I'm a bit confused. Could you give me an example
where this would affect your processes.

from crmsh.

Understood, thank you for your explanation. We will adjust our usage accordingly and rely on error codes only as we should.

from crmsh.