Comment # 3 on bug 917638 from
>> In which circumstance is this necessary? Is it when hb_report is called by
>> crmsh?
>
>
>Yes. Something like adding "-l /var/log/pacemaker.log" or similar.

Is there a concrete situation where you needed this? I am trying to understand
what the use case is so I can know if any suggestion I make would actually
work. :)

I don't like relying on environment variables, that seems fragile and requires
being able to change the tool as well...

I think the crmsh configuration option might work, but at the same time I feel
like it's uglier than is necessary..

The crmsh getopt choice I think is confusing.

How about a special command under the history level? Something like

crm history
  report_options -l /var/log/pacemaker.log
  ...

> To me the current hb_report format looks fine. Or would you want to change that?

Well, I put it in the far distant future because I am not sure it is worth the
actual effort. I don't have any major reason to replace hb_report right now,
but thinking ahead, it seems like a worthwhile goal at some point to have crmsh
do that part.

For one thing, hb_report has its own way of figuring out what OCF_ROOT and
other system constants like that should be, which may result in it using a
different setting than crmsh. It would be better to have that all configured by
crmsh in one place.


You are receiving this mail because: