On Mon, Sep 07, 2015 at 06:25:26PM +0200, Miroslav Lichvar wrote:
> Upgrade the message level to info so the user can see it, but print it
> at most once per 5 minutes to not spam the syslog.
> ---
> port.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/port.c b/port.c
> index 9c804cf..527cd6b 100644
> --- a/port.c
> +++ b/port.c
> @@ -1688,8 +1688,8 @@ static void process_delay_resp(struct port *p, struct
> ptp_message *m)
> }
> if (rsp->hdr.logMessageInterval < -10 ||
> rsp->hdr.logMessageInterval > 22) {
> - pr_debug("port %hu: ignore bogus delay request interval 2^%d",
> - portnum(p), rsp->hdr.logMessageInterval);
> + LIMIT_RATE(300, pr_info("port %hu: ignore bogus delay request
> interval 2^%d",
> + portnum(p),
> rsp->hdr.logMessageInterval));
I like this feature, but it would be so much nicer to have:
pl_debug(300, "port %hu: ignore bogus delay request interval
2^%d",
portnum(p), rsp->hdr.logMessageInterval);
I mean having one new pl_ macro for each pr_ macro.
What do you think?
Thanks,
Richard
------------------------------------------------------------------------------
Monitor Your Dynamic Infrastructure at Any Scale With Datadog!
Get real-time metrics from all of your servers, apps and tools
in one place.
SourceForge users - Click here to start your Free Trial of Datadog now!
http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140
_______________________________________________
Linuxptp-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
