New log_max_line_length option.

Code Issues Proposed changes

Log lines can get quite large, as we previously noticed with rsync error
log lines. We added a setting to cap those, but it really looks like we
should have just done this overall limit. We noticed the issue when we
switched to UDP syslogging and it would occasionally blow past the 16436
lo MTU! This causes Python's logging code to get an error and hilarity
ensues.
Change-Id: I44bdbe68babd58da58c14360379e8fef8a6b75f7

This commit is contained in:

gholt

2014年05月22日 19:37:53 +00:00

parent 553007865f

commit 2d00f7b7ba

10 changed files with 114 additions and 3 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download Patch File Download Diff File Expand all files Collapse all files

3
etc/account-server.conf-sample

View File

@@ -21,6 +21,9 @@

# log_facility = LOG_LOCAL0

# log_level = INFO

# log_address = /dev/log

# The following caps the length of log lines to the value given; no limit if

# set to 0, the default.

# log_max_line_length = 0

#

# comma separated list of functions to call to setup custom log handlers.

# functions get passed: conf, name, log_to_console, log_route, fmt, logger,

New log_max_line_length option.

3 etc/account-server.conf-sample Unescape Escape View File

3
etc/account-server.conf-sample

View File