~/.cache/upstart/ logs are not rotated often enough

Bug #1306361 reported by Dimitri John Ledkov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
upstart (Ubuntu)
Fix Released
Medium
Dimitri John Ledkov
Trusty
Fix Released
Medium
Dimitri John Ledkov

Bug Description

[Impact]

 * ~/.cache/upstart contains user session logs which are rotated upon login. But due to excellent hibernate & syspend/resume people can spend weeks without re-logging in. Thus those logs can grow uncontrollably.

[Test Case]

 * Monitor logs in ~/.cache/upstart note how many of them can be uncompressed
 * With updated packages, those should be rotated every hour (17 minutes past the hour by default)

[Regression Potential]

 * user session logrotation was already inplace, we are now adding one more start on condition to it, which is triggered via system cron.hourly

Related branches

Changed in upstart (Ubuntu Trusty):
status: New → In Progress
importance: Undecided → Medium
assignee: nobody → Dimitri John Ledkov (xnox)
Revision history for this message
James Hunt (jamesodhunt) wrote :

Confused as to why this bug has been raised? I have already fixed this issue to rotate logs hourly in 1.12.1-0ubuntu2 ?? Also why 17 minutes past the hour exactly?

Revision history for this message
Dimitri John Ledkov (xnox) wrote :

James, i've raised this bug, in retro-spect as a reference to include in the debian/changelog for your changes before uploading 1.12.1-0ubuntu2. This way this upstart upload can become SRU if release team so wishes.

Changed in upstart (Ubuntu Trusty):
status: In Progress → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package upstart - 1.12.1-0ubuntu4

---------------
upstart (1.12.1-0ubuntu4) trusty; urgency=medium

  [ Adam Conrad ]
  * Disable chroot sessions by default, add an option to enable chroot
    sessions. (LP: #1277594)
 -- Dimitri John Ledkov <email address hidden> Fri, 11 Apr 2014 22:31:21 +0100

Changed in upstart (Ubuntu Trusty):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.