Opened 6 years ago

Closed 6 years ago

#790 closed defect (fixed)

RouterClock loglevel change

Reported by: guest Owned by:
Priority: minor Milestone: 0.9.4
Component: router/general Version: 0.9.3
Keywords: Cc:
Parent Tickets:

Description

Would it be more practical to log:

getLog().warn("Ignoring update from a stratum " + stratum +
                              " clock, we recently had an update from a stratum " + _lastStratum + " clock");

to INFO and higher?

Subtickets

Change History (3)

comment:1 Changed 6 years ago by zzz

why?

comment:2 Changed 6 years ago by guest

zzz, since Im not sure why the language Warn is being used here? Not sure why i should be warned that my routers clock is good. And my log is full of it

comment:3 Changed 6 years ago by zzz

  • Resolution set to fixed
  • Status changed from new to closed

Changed from warn to debug in e04877f3444044f5ef125fb45263a241b21c56da.

You may control what gets logged on /configlogging in the console, if anything else is filling your logs and that's a problem. Yes, lots of things that are logged at the WARN level should probably be lower, this isn't the only one.

Note: See TracTickets for help on using tickets.