Project

General

Profile

Actions

Todo #9734

closed

Todo #8350: Remove clog in favor of standard syslogd or syslogd alternative with rotation via newsyslog or logrotate

Re-evaluate log size, line defaults, and limits

Added by Jim Pingle about 2 years ago. Updated over 1 year ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Logging
Target version:
Start date:
09/08/2019
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
Release Notes:

Description

The current limits for log sizes, default lines to display, and maximum lines that can be shown are all from times when systems were much smaller/less powerful.

Log size may still be OK now that rotated copies don't count against it, but needs checked.

Default log lines to display should probably be higher, 250-500 or so.

Max lines to display is currently limited to 2000 but should be much higher.

Actions #1

Updated by Jim Pingle about 2 years ago

  • Status changed from New to Feedback
  • % Done changed from 0 to 100
Actions #2

Updated by Jim Pingle almost 2 years ago

  • Status changed from Feedback to Resolved

These all seem to be OK for now. Can revisit if necessary.

Actions #3

Updated by Sean McBride over 1 year ago

I was going to file a similar ticket, but found this one searching for "511488"...

I'm not sure how typical my setup is, but at the default of 511488 bytes, my firewall log rotates every 3 minutes. I had made a firewall rule to catch which office PC has malware, but struggled to find results searching the logs, and finally found the reason was the tiny default log size.

~20 log files x 500 KiB each is still only 10 MiB total.

A 32 GiB microSD card costs something like $15 USD. Enough for 1000x the size of default logs.

Do most pfsense users really have so little storage? Considering the importance of the logs, I'd argue the default should be increased 10x or 100x.

Actions

Also available in: Atom PDF