[Bug 1578628] Re: Upstart log files are not reopened after rolling

[Pat McGowan]

** Description changed:

  Seen on stable and proposed vivid based touch images
  I noticed on two of my devices that after a scheduled rolling of the files in /var/log/upstart that there were no active *.log files at all.
  The config for upstart includes nocreate but this has always been this way.
  Is this intended or did something change in logrotate?
  A similar bug report states that the files will be opened on a subsequent write from the upstart process, but this is clearly not happening.
+ 
+ See http://askubuntu.com/questions/481236/upstart-not-reopening-log-files-on-logrotation
+ and perhaps bug #1350782

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/1578628

Title:
  Upstart log files are not reopened after rolling

Status in Canonical System Image:
  New
Status in upstart package in Ubuntu:
  New

Bug description:
  Seen on stable and proposed vivid based touch images
  I noticed on two of my devices that after a scheduled rolling of the files in /var/log/upstart that there were no active *.log files at all.
  The config for upstart includes nocreate but this has always been this way.
  Is this intended or did something change in logrotate?
  A similar bug report states that the files will be opened on a subsequent write from the upstart process, but this is clearly not happening.

  See http://askubuntu.com/questions/481236/upstart-not-reopening-log-files-on-logrotation
  and perhaps bug #1350782

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1578628/+subscriptions