https://bugzilla.redhat.com/show_bug.cgi?id=1323521
Frank Ch. Eigler <fche@xxxxxxxxxx> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|CLOSED |NEW
Resolution|WONTFIX |---
Keywords| |Reopened
--- Comment #4 from Frank Ch. Eigler <fche@xxxxxxxxxx> ---
> > [...] Have you tested this scenario before making this assertion?
> > [...] avoid paying its performance cost
>
> You seem to be asking me to prove that that a hypothetical bug you've opened
> exists. However, I see no evidence of a problem, nor would I expect to, so
> I tend to think we should spend time on more worthwhile pursuits.
The bug plainly exists in the current code. A large-fanout central pmie server
will flood its own local pmcd with SIGHUPS, 1 per minute per remote server.
Your assertion was that this is free of consequence. Have you ever tested what
a pmcd does when it's given a SIGHUP multiple times a second? (Plus a syslog
message for each?)
> > Hand-editing default configuration files is not helpful advice, esp. [...]
>
> Oh, a misunderstanding perhaps - this is all pmieconf-driven, there's no
> hand-editing involved here.
The point is that you suggested editing the pmieconf-generated files to remove
the useless & possibly-harmful pmsignal clause. That is an impractical
solution.
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug
https://bugzilla.redhat.com/token.cgi?t=SMD2LokBOt&a=cc_unsubscribe
|