In fact the man page seems to be completely out of sync with reality. None of minage, maxage, minsize and maxsize appear to work at all despite being documented there. Minage is read at least (according to debug output), but then still ignored. Specifying minsize or maxsize has no effect, logs are rotated when they hit 1 M regardless. At least the plain `size` directive does appear to work as documented.
Viestit paikassa Launchpad
The man page for logrotate says ”Each configuration file can set global options (local definitions override global ones, and later definitions override earlier ones)”. This is inconsistent with how it actually behaves.
== Steps to reproduce ==
$ logrotate –version
Default mail command: /usr/bin/mail
Default compress command: /bin/gzip
Default uncompress command: /bin/gunzip
Default compress extension: .gz
Default state file path: /var/lib/logrotate/status
ACL support: yes
SELinux support: yes
$ mkdir /tmp/logrotest
$ cd /tmp/logrotest
$ touch test.log
$ touch other.log
$ cat >logrotate.conf
$ logrotate –state /tmp/logrostate logrotate.conf
== What happens ==
error: logrotate.conf:5 duplicate log entry for /tmp/logrotest/test.log
== What I expect to happen instead ==
No error, test.log being processed with its specific, later-defined directives.
If a simple accidental click somewhere could cause this, that’s a loaded gun pointed at the user’s toe
@Julian: I’d argue that if a simple accidental click somewhere can cause this, that’s a loaded gun pointed at the user’s toe, and hence a bug in the installer.
@Brian: I’ll try the 22.04 images. I’ve kept trying with 20.04.5, but have yet to find another instance of this occurring, so it’s obviously not easy to trigger.
I’m not particularly troubled by this issue (and the original reporter doesn’t seem to be either), so feel free to adjust ’Importance’ accordingly.
@Olivier: Sure. This VM was just for testing purposes, so there shouldn’t be anything confidential here.
Looks like the deb line for updates is missing entirely from sources.list in this install; only the deb-src is there.
@Simon Here goes, although now it just shows both at 9.7, and 9.9 not yet available. Before I downgraded libc6 it obviously showed libc6 at 9.9.
I also tried to reproduce the issue in a fresh VM, but those kept getting 9.9 for all the packages, so installing build-essential caused no issues.
I don’t have in-depth knowledge about phased updates, but this looked like as if downloading the updates during installation was not yet affected by phased updates (and hence got libc 9.9), but, after the installation was completed, the system got cast into a ”still at 9.7” group of phased updates, and so libc6-dev (et al) could not be installed.
Just got hit by the same issue in a VM after a fresh install of 20.04.5. I chose ”Minimal installation”, ticked ”Download updates while installing”, and installed the remaining updates post-install.
After that the first thing I tried to do was to install build-essential, which failed, because the version of libc6 was out of sync with the rest of the libc6* packages: libc6 was already at 2.31-0ubuntu9.9, while e.g. libc6-dev was still only available as 2.31-0ubuntu9.7.
I tried switching from my local archive (fi.archive.ubuntu.com) to the main one (archive.ubuntu.com), but that made no difference. I had to downgrade libc6 to 2.31-0ubuntu9.7 to be able to install build-essential.
-s (silent) is also undocumented. There’s a confusing distinction between it and -q (quiet), where the latter isn’t quiet in the usual sense; -s is needed to silence non-error output entirely. There’s useless output even when called entirely without options:
$ pngcrush CPU time decode 0.000000, encode 0.000000, other 0.000000, total 0.000002 sec $ pngcrush -q CPU time decode 0.000000, encode 0.000000, other 0.000000, total 0.000002 sec $ pngcrush -s $
This is pngcrush 1.8.13-0.1 on focal.
Seems to be fixed in VLC 22.214.171.124-1 (Ubuntu 20.04); at least I haven’t been able to reproduce it anymore.