logrotate limit of 10mb for /var/log/syslog is not so useful for debugging
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical System Image |
Fix Released
|
High
|
Unassigned | ||
lxc-android-config (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
lxc-android-config (Ubuntu RTM) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
current build number: 194
device name: krillin
channel: ubuntu-
last update: 2015-01-14 14:01:42
version version: 194
version ubuntu: 20150114
version device: 20150113-2a2e4c5
version custom: 20150112-494-23-173
/var/log/syslog {
# don't use time based rotation, but size-based
size 10M
# do not keep old files at all
rotate 0
# don't use compression
nocompress
postrotate
service rsyslog reload >/dev/null 2>&1 || true
endscript
}
Only 10MB makes it harder to debug as sometimes we need a bit more data in order to get useful results from the debug log. One example is looking for suspend failures, since we can't really go back much in time when investigating syslog.
20MB would already be enough for now.
Changed in canonical-devices-system-image: | |
milestone: | none → ww05-2015 |
status: | New → Confirmed |
importance: | Undecided → High |
Changed in canonical-devices-system-image: | |
status: | Confirmed → Fix Released |
This bug was fixed in the package lxc-android-config - 0.213
---------------
lxc-android-config (0.213) vivid; urgency=medium
* Increase log size for syslog, useful for debugging (LP: #1410937)
-- Ricardo Salveti de Araujo <email address hidden> Wed, 14 Jan 2015 17:46:18 -0200