verbosity for logrotate

Bug #1753946 reported by Sergey Ivanov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
logrotate (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

User has modified /etc/logrotate.conf file such that it includes another file /path/to/own/other_logrotate.conf:
...
include /path/to/own/other_logrotate.conf
...

Now run under root:

logrotate -v /etc/logrotate.conf

Expected result:
verbosity related to other logrotate file should be very same as if we run other logrotate directly
i.e:
logrotate -v /etc/logrotate.conf should have same output related to /path/to/own/other_logrotate.conf
as if we run directly
logrotate -v /path/to/own/other_logrotate.conf

Actual result:
logrotate -v /etc/logrotate.conf has empty output regarding to /path/to/own/other_logrotate.conf

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: logrotate 3.8.7-2ubuntu2.16.04.2
ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-36-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Mar 7 10:33:11 2018
InstallationDate: Installed on 2018-01-23 (42 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
SourcePackage: logrotate
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.logrotate.conf: 2018-03-07T10:33:03.883000

Revision history for this message
Sergey Ivanov (icegood1980) wrote :
Changed in logrotate (Ubuntu):
status: New → Invalid
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.