On 17/11/14 12:25, Gian Uberto Lauri wrote:
There were other poor design choices, it seems that Debian maintainers have fixed some of them (i.e. renaming network devices), other seems to be still there (binary logs...).
A default Debian jessie configuration has persistent text logs in /var/log written by rsyslog, and *volatile* binary logs in /run/log/journal written by systemd-journald. Removing the binary logs completely disables functionality of the systemd suite which an administrator familiar with systemd would expect to be present by default.
Administrators of systemd-based systems who wish to turn off the binary log can, of course, simply add the line
Storage=noneto the [Journal] section of /etc/systemd/journald.conf, at which point systemd-journald will simply forward all log entries directly to rsyslog without writing them to a binary file.
If installing, or upgrading to, jessie resulted in a configuration with *only* binary logs, and this was not the obvious foreseeable result and intent of a deliberate administrator action taken during the installation/upgrade procedure, then that is probably what we call a *bug*, and is the sort of thing that is why Debian has a "testing" branch.