| 2016-05-05 13:14:33 |
Pat McGowan |
bug |
|
|
added bug |
| 2016-05-05 13:14:58 |
Pat McGowan |
description |
Seen on stable and proposed
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. |
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. |
|
| 2016-05-05 13:15:10 |
Pat McGowan |
bug task added |
|
upstart (Ubuntu) |
|
| 2016-05-05 13:24:54 |
Pat McGowan |
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. |
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 |
|
| 2016-05-18 21:50:25 |
Pat McGowan |
canonical-devices-system-image: status |
New |
Confirmed |
|
| 2016-05-18 21:50:43 |
Pat McGowan |
canonical-devices-system-image: milestone |
|
backlog |
|
| 2016-06-10 16:03:43 |
Pat McGowan |
canonical-devices-system-image: importance |
Undecided |
High |
|
| 2016-06-10 16:03:46 |
Pat McGowan |
canonical-devices-system-image: milestone |
backlog |
12 |
|
| 2016-06-30 21:04:22 |
Pat McGowan |
canonical-devices-system-image: milestone |
12 |
backlog |
|
