Ticket #359 (closed defect: fixed)

Opened 12 years ago

Last modified 11 years ago

Sending all of dmesg to wslogger is kind of obnoxious

Reported by: geofft Owned by:
Priority: normal Milestone: Summer 2010 (Lucid Deploy)
Component: -- Keywords:
Cc: Fixed in version:
Upstream bug:

Description

cfox reports that the entire kernel boot process is sent to wslogger (see /mit/cfox/Public/hayden-1 for an example); indeed, our syslog transformer adds
*.warning;kern,user,auth.info @WSLOGGER.MIT.EDU
That probably wants to be restricted to only high-priority kernel messages.

Change History

comment:1 Changed 11 years ago by broder

Did we...ever decide what we wanted to do with this ticket? It's certainly easy to drop kern.info from the configuration, but does it make sense to keep logging the user or auth facilities? I guess one aspect is that auth.info is that it gives us a record if somebody does something sketchy. I have no clue what goes to the user facility.

I think we sort of left this off with "well, it depends on what we're looking for from centralized syslogs," and I'm not sure what we are looking for, or even who it is that's looking for it. I think this may be something to bring up at release-team for decision.

comment:2 Changed 11 years ago by jdreed

  • Milestone set to The Distant Future

comment:3 Changed 11 years ago by jdreed

  • Status changed from new to proposed

comment:4 Changed 11 years ago by jdreed

  • Milestone changed from The Distant Future to Summer 2010 (Lucid Deploy)

comment:5 Changed 11 years ago by broder

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

Moved to production - machines with syslog-config should now only log *.warning;user,auth.info to urania.

Note: See TracTickets for help on using tickets.