Bug#698555: unblock: systemd/44-8
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package systemd It contains the following two fixes: systemd (44-8) unstable; urgency=low * Team upload. * Use comment=systemd.* syntax in systemd.mount man page. The mount/util-linux version in wheezy is not recent enough to support the new x-systemd* syntax. Closes: #697141 * Don't enable persistent storage of journal log files. The journal in v44 is not yet mature enough. -- Michael Biebl bi...@debian.org Sat, 19 Jan 2013 20:05:05 +0100 The journal related changes probably deserve a couple of words: The journal in v44 is still pretty new and not yet very robust. Under certain circumstances (e.g. system crash) the journal can become corrupted. While newer versions are much more likely to recover from such a situation, in v44 one needs to remove the journal files in /var/log/journal manually. By not making the journal files persistent, after a reboot the journal will be working again in any case. We also still ship a syslog by default in Debian, so we do have long-term logs. So we decided to not ship /var/log/journal in the package for wheezy. In that case systemd-journald will not store any log files on disk. Full diff between 44-7 and 44-8 is attached. debdiff will unfortunately generate a more verbose diff due to the way systemd handles the git-export patches Cheers, Michael (on behalf of the systemd maintainers) unblock systemd/44-8 -- System Information: Debian Release: 7.0 APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#698555: unblock: systemd/44-8
On 2013-01-20 13:53 +0100, Michael Biebl wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package systemd It contains the following two fixes: systemd (44-8) unstable; urgency=low * Team upload. * Use comment=systemd.* syntax in systemd.mount man page. The mount/util-linux version in wheezy is not recent enough to support the new x-systemd* syntax. Closes: #697141 * Don't enable persistent storage of journal log files. The journal in v44 is not yet mature enough. -- Michael Biebl bi...@debian.org Sat, 19 Jan 2013 20:05:05 +0100 The journal related changes probably deserve a couple of words: The journal in v44 is still pretty new and not yet very robust. Under certain circumstances (e.g. system crash) the journal can become corrupted. While newer versions are much more likely to recover from such a situation, in v44 one needs to remove the journal files in /var/log/journal manually. By not making the journal files persistent, after a reboot the journal will be working again in any case. We also still ship a syslog by default in Debian, so we do have long-term logs. So we decided to not ship /var/log/journal in the package for wheezy. In that case systemd-journald will not store any log files on disk. Are current users of systemd advised to remove /var/log/journal themselves? Having used systemd exclusively for a few weeks, I discovered a 23 Megabyte system.journal file which apparently never got rotated or truncated. Cheers, Sven -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#698555: unblock: systemd/44-8
On 20.01.2013 15:18, Sven Joachim wrote: On 2013-01-20 13:53 +0100, Michael Biebl wrote: So we decided to not ship /var/log/journal in the package for wheezy. In that case systemd-journald will not store any log files on disk. Are current users of systemd advised to remove /var/log/journal themselves? Having used systemd exclusively for a few weeks, I discovered a 23 Megabyte system.journal file which apparently never got rotated or truncated. Nuking log files is always tricky business. That's why I decided to not remove existing journal files on upgrades for sid users. Some sid users might have decided to uninstall (r)syslog and use the journal exclusively. They would certainly be angry, if a postinst just deleted those logs. It depends on your usage of the journal. As for the size of the journal file: That is definitely in the normal range. See man 5 systemd-journald.conf. By default the persistent journal files will take up to 5% of the file system where /var/log/journal resides on. You can tweak all those settings in the corresponding conf file. Cheers, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
