On Thu, 2019-11-14 at 15:22 +0100, Ulrich Windl wrote:
> > > > Jehan-Guillaume de Rorthais schrieb am
> > > > 14.11.2019 um
>
> 15:17 in
> Nachricht <20191114151719.6cbf4e38@firost>:
> > On Wed, 13 Nov 2019 17:30:31 ‑0600
> > Ken Gaillot wrote:
> > ...
> > > A longstanding pain point in the
On Thu, 2019-11-14 at 14:54 +0100, Jan Pokorný wrote:
> On 13/11/19 17:30 -0600, Ken Gaillot wrote:
> > This fixes some more minor regressions in crm_mon introduced in
> > rc1.
> > Additionally, after feedback from this list, the new output format
> > options were shortened. The help is now:
> >
On Wed, 13 Nov 2019 17:30:31 -0600
Ken Gaillot wrote:
...
> A longstanding pain point in the logs has been improved. Whenever the
> scheduler processes resource history, it logs a warning for any
> failures it finds, regardless of whether they are new or old, which can
> confuse anyone reading
On 13/11/19 17:30 -0600, Ken Gaillot wrote:
> This fixes some more minor regressions in crm_mon introduced in rc1.
> Additionally, after feedback from this list, the new output format
> options were shortened. The help is now:
>
> Output Options:
> --output-as=FORMAT Specify output format
On 11/14/19 9:50 AM, Ulrich Windl wrote:
> Hi!
>
> recently I noticed that hb_report in SLES12 SP4 issues a SysRq to dump the
> state of all tasks to syslog. That will be about 3 lines for our server.
> Is that intended?
I think so according to:
Hi!
recently I noticed that hb_report in SLES12 SP4 issues a SysRq to dump the
state of all tasks to syslog. That will be about 3 lines for our server. Is
that intended?
kernel: [271678.727330] sysrq: SysRq : Show State
kernel: [271815.893786] sysrq: SysRq : Show State
kernel:
