Your message dated Sun, 28 Feb 2016 23:53:07 +0000
with message-id <e1aab99-00033u...@franck.debian.org>
and subject line Bug#815020: fixed in systemd 229-2
has caused the Debian Bug report #815020,
regarding breaks coredump handling for systems without systemd-coredump
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
815020: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815020
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: systemd
Version: 229-1
Hi,
systemd contains the following line (src/core/main.c):
(void)
write_string_file("/proc/sys/kernel/core_pattern", "|/bin/false", 0);
The intent is that at some later point, systemd-coredump is started,
which then sets it to something more useful.
However, in Debian, systemd-coredump is in a separate package that
systemd itself does not depend on. As a result, if systemd is used as
PID1, but systemd-coredump is not installed, all core dumps are thrown
into the bit bucket; not just those that are generated during bootup,
but all core dumps after boot, too.
They're still generated, however, since systemd also sets the default
soft resource limit on core file size ("ulimit -c") to the "unlimited"
value, rather than having the hard limit be unlimited and the soft limit
be set at 0.
This is not an ideal situation:
- Generating a core dump, especially in case of a program that uses a
lot of memory at the time where the dump is generated, requires some
processing. If the core dump is thrown away, this is wasted processing
time. If the system is loaded (e.g., because something is forking and
segfaulting a lot), this is problematic behaviour. By setting the soft
core file size resource limit to 0, core dumps aren't even generated,
improving performance.
- The kernel.core_pattern sysctl setting is a system-wide setting; it is
not possible to modify this other than by using CAP_SYS_ADMIN (IIUC)
permissions. In contrast, the resource limits are per-process
configuration; any process can change its resource limits at will.
This allows the system to have a default of "no core dumps", but at
the same time, allows a developer or a system administrator to
temporarily enable core dumps for a particular process, without
requiring administrator capabilities.
I'm sure systemd-coredump replicates some of the above, but it isn't
always the best choice to have a core dump be piped into a process, and
therefore using the traditional "just dump everything to disk" logic can
still be beneficial.
-- Package-specific info:
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500,
'oldstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.3.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=nl_BE.UTF-8, LC_CTYPE=nl_BE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages systemd depends on:
ii adduser 3.113+nmu3
ii libacl1 2.2.52-3
ii libapparmor1 2.10-3
ii libaudit1 1:2.4.5-1
ii libblkid1 2.27.1-3
ii libc6 2.21-8
ii libcap2 1:2.24-12
ii libcap2-bin 1:2.24-12
ii libcryptsetup4 2:1.7.0-2
ii libgcrypt20 1.6.5-2
ii libgpg-error0 1.21-2
ii libkmod2 22-1
ii liblzma5 5.1.1alpha+20120614-2.1
ii libmount1 2.27.1-3
ii libpam0g 1.1.8-3.2
ii libseccomp2 2.2.3-3
ii libselinux1 2.4-3
ii libsystemd0 229-1
ii mount 2.27.1-3
ii util-linux 2.27.1-3
Versions of packages systemd recommends:
ii dbus 1.10.6-1
ii libpam-systemd 229-1
Versions of packages systemd suggests:
pn systemd-container <none>
pn systemd-ui <none>
Versions of packages systemd is related to:
ii udev 229-1
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: systemd
Source-Version: 229-2
We believe that the bug you reported is fixed in the latest version of
systemd, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 815...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Martin Pitt <mp...@debian.org> (supplier of updated systemd package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Sun, 28 Feb 2016 22:16:12 +0100
Source: systemd
Binary: systemd systemd-sysv systemd-container systemd-journal-remote
systemd-coredump libpam-systemd libnss-myhostname libnss-mymachines
libnss-resolve libsystemd0 libsystemd-dev udev libudev1 libudev-dev udev-udeb
libudev1-udeb systemd-dbg
Architecture: source amd64
Version: 229-2
Distribution: unstable
Urgency: medium
Maintainer: Debian systemd Maintainers
<pkg-systemd-maintain...@lists.alioth.debian.org>
Changed-By: Martin Pitt <mp...@debian.org>
Description:
libnss-myhostname - nss module providing fallback resolution for the current
hostname
libnss-mymachines - nss module to resolve hostnames for local container
instances
libnss-resolve - nss module to resolve names via systemd-resolved
libpam-systemd - system and service manager - PAM module
libsystemd-dev - systemd utility library - development files
libsystemd0 - systemd utility library
libudev-dev - libudev development files
libudev1 - libudev shared library
libudev1-udeb - libudev shared library (udeb)
systemd - system and service manager
systemd-container - systemd container/nspawn tools
systemd-coredump - tools for storing and retrieving coredumps
systemd-dbg - system and service manager (debug symbols)
systemd-journal-remote - tools for sending and receiving remote journal logs
systemd-sysv - system and service manager - SysV links
udev - /dev/ and hotplug management daemon
udev-udeb - /dev/ and hotplug management daemon (udeb)
Closes: 814566 814667 815020 815586 815793 815884 816132
Changes:
systemd (229-2) unstable; urgency=medium
.
* time-util: map ALARM clockids to non-ALARM clockids in now(), to work on
architectures which don't support CLOCK_BOOTTIME_ALARM. Fixes FTBFS on
many architectures.
* debian/systemd.postinst: Add missing newline to /etc/adjtime migration.
(See #699554)
* debian/systemd.postinst: Only try to enable tmp.mount if we actually
copied it to /etc. Don't try to enable a generated unit. (LP: #1545707)
* debian/tests/boot-and-services: Increase timeouts of test_bash_crash from
5 to 10 seconds, and sync the journal after every iteration.
* debian/extra/checkout-upstream: Try again after one minute if git checkout
fails, to avoid failures from transient network errors.
* debian/tests/systemd-fsckd: Use grub.d/50-cloudimg-settings.cfg as a
template for generating our custom one instead of 90-autopkgtest.cfg. The
latter does not exist on non-x86 architectures and is not relevant for
this test.
* debian/tests/boot-and-services: Skip journal test for test_bash_crash when
running against upstream, as this currently fails most of the time. To be
investigated.
* debian/tests/networkd: Skip test_coldplug_dhcp_ip6 when running against
upstream, as this is brittle there. To be investigated.
* debian/tests/bootchart: Skip test if bootchart is not available or
testing in upstream mode. bootchart got removed from master and will be
moved to a separate repository.
* debian/tests/boot-and-services: Show verbose journal output on failure in
nspawn test, and sync journal before.
* Move systemd-coredump socket and service into systemd-coredump binary
package.
* Revert changing the default core dump ulimit and core_pattern. This
completely breaks core dumps without systemd-coredump. It's also
contradicting core(8). (Closes: #815020)
* Fix addresses for type "sit" tunnels. (Closes: #816132)
* networkd: Go back to letting the kernel handle IPv6 router advertisements,
as networkd's own currently has too many regressions. Thanks to Stefan
Lippers-Hollmann for investigating this! (Closes: #814566,
#814667, #815586, #815884, #815793)
Checksums-Sha1:
156fa5d375e0c8b78236e63bab76b9ac5d27431d 4073 systemd_229-2.dsc
710d9893f3be794af273690d23278018c1cd4a24 120360 systemd_229-2.debian.tar.xz
4a514b66b399768c86e558af3dfbc4aa2b0d6253 85468
libnss-myhostname_229-2_amd64.deb
2a02acf3325462c1708092416a668ce095c0dede 165672
libnss-mymachines_229-2_amd64.deb
34f58c3a13b468af8803661450a427520b8dc33c 164916 libnss-resolve_229-2_amd64.deb
7e289fa3cb5b743eb49ccdf5d7a62fb152a0f0ec 167540 libpam-systemd_229-2_amd64.deb
e11a01a97153d5b6da82327cd8bdd96ea7f1f5ed 211292 libsystemd-dev_229-2_amd64.deb
0aee070430db6b8f87920352e9117aa06d376bb9 254720 libsystemd0_229-2_amd64.deb
f4138aba406223ade1ad6af832b81bff6fdd27cc 71598 libudev-dev_229-2_amd64.deb
24a4149667595df98aa618a9474e02741d30b368 47798 libudev1-udeb_229-2_amd64.udeb
8f3f64e84bafa88d09952c5159f9b81a8e9f84dc 104192 libudev1_229-2_amd64.deb
0ea74f0b64e0ece3104e2e7d47ec4d6961e03d6a 701838
systemd-container_229-2_amd64.deb
856d3b5bbdd54786258a5bb1d7e9eb9737fd09f2 159860
systemd-coredump_229-2_amd64.deb
c05f3eacb6b428bb48348d36ea0f24fb8be1fd4f 30101104 systemd-dbg_229-2_amd64.deb
8154fe7231f77332bf6f27da81709639e0718acf 315850
systemd-journal-remote_229-2_amd64.deb
b66616a95d942dae475835f577eec0de120c86e6 61742 systemd-sysv_229-2_amd64.deb
31f95d47c325286a304e58c72f4591b058eba2e7 3654292 systemd_229-2_amd64.deb
eaeb339dbdc48e27a9fe4a0a23470a0b402e5602 266906 udev-udeb_229-2_amd64.udeb
9bc0f1b3fb361f98eaac88a2df1ac06797c07b17 1039278 udev_229-2_amd64.deb
Checksums-Sha256:
08ac5b74baa76f8724d3ef587dd4b6a9f5c6a5020ec30dffb384a17953542ae3 4073
systemd_229-2.dsc
a0b7f59fc44d392ab68b551c4eacd9ddb6299f95f1f23457b4dcdc7b46d2a982 120360
systemd_229-2.debian.tar.xz
ab557b54ec9855420dddb55cf3d32fb0c7a8f7232a737f5bb1d9a1df482fc4ad 85468
libnss-myhostname_229-2_amd64.deb
e5023006b6e51d22ba8e6c2c9c7e946646d953e2ddeee66255176684fb08b621 165672
libnss-mymachines_229-2_amd64.deb
ef37d07be01e3cdd8611ab246526153886168b61005fe5eaa0286e6d529afd90 164916
libnss-resolve_229-2_amd64.deb
878b549fe21459845d118792d3dcee75247db593d3f26c062850e399a0bf84ed 167540
libpam-systemd_229-2_amd64.deb
48740d20af0fce47dc56a699c68999f9c152ffec2ff4f3153729f0d4344bb0bb 211292
libsystemd-dev_229-2_amd64.deb
58d3b402807bf83e2788d938c87fd36ce0a9f7e0b3cc9ece806366fb18618dd2 254720
libsystemd0_229-2_amd64.deb
f5126ce29963d5bd0ab07fdc0142898efacc1eee726cd21e9b22484b8dd8f3a1 71598
libudev-dev_229-2_amd64.deb
37453c3db05a4894ae992195374bd555c8761e766f29b9ae41dc11c713e9eff9 47798
libudev1-udeb_229-2_amd64.udeb
00ae505cf1d03b08a1fb0a855eaea941f577420ac1729ef9f968f23e685a754c 104192
libudev1_229-2_amd64.deb
9d42e205f855fac18fc7404ac3389cbfbb23c6f5c8b21296b156228860175ecf 701838
systemd-container_229-2_amd64.deb
55f7de73e9e138075965672b0efefcb241c57d9477284bee2fd28d4a3ffbe13a 159860
systemd-coredump_229-2_amd64.deb
09c3571913d93e676d2442d5fe967f1d762ffb75a39ea936ba4497a7466e23f6 30101104
systemd-dbg_229-2_amd64.deb
767329c159948bf1b66432b654748d90a7ba8189721ef791f6ee9d8da9806f56 315850
systemd-journal-remote_229-2_amd64.deb
f9f931e8607392e968c61c8433edf23a9535e92cab84caa176e82e65662b6bc4 61742
systemd-sysv_229-2_amd64.deb
17a0703ae4859dd9ed74c0b65753b4e714cec2e08ae8c4f42dfe9bf54d8d96e3 3654292
systemd_229-2_amd64.deb
1042cf1cdf67ccff03c2009d94e230344f5e31561ec3d4daa92be9ff353a563d 266906
udev-udeb_229-2_amd64.udeb
fecee4479dfcf81d4657bff51fba2ab0f0d5f76020e8ad5577faeb663983d9b2 1039278
udev_229-2_amd64.deb
Files:
a2af5a1ab48dc08cf0d46fd377b11700 4073 admin optional systemd_229-2.dsc
da34adb504cc69ca1c00265fb85cdb91 120360 admin optional
systemd_229-2.debian.tar.xz
7a0aedda643c8c495f0dfef7b180426c 85468 admin extra
libnss-myhostname_229-2_amd64.deb
084324f2bb552d1d8d6dbd51b30a85e3 165672 admin extra
libnss-mymachines_229-2_amd64.deb
73865f1584f7f04637cd2a1a14712703 164916 admin extra
libnss-resolve_229-2_amd64.deb
0d21cebf41341ca0cfea94738ac71188 167540 admin optional
libpam-systemd_229-2_amd64.deb
7123ee343f67ace0e7833855671c437c 211292 libdevel optional
libsystemd-dev_229-2_amd64.deb
8d5d495b19b7a566188f2ba02f6ea0e0 254720 libs optional
libsystemd0_229-2_amd64.deb
75a443208963585a60b40f7ef3c4ee2c 71598 libdevel optional
libudev-dev_229-2_amd64.deb
46e8d2461bf681fca506ff291c7d470f 47798 debian-installer optional
libudev1-udeb_229-2_amd64.udeb
678c7c4e80bdda5afb5fbda1d71b1b0b 104192 libs important libudev1_229-2_amd64.deb
0730ebcfc900fb78ca0f2c5313b4d6c5 701838 admin optional
systemd-container_229-2_amd64.deb
4b065b2dd1afc5b2a82d9fc315c482d4 159860 admin optional
systemd-coredump_229-2_amd64.deb
c3be434bba6294a9804278e75aa0d828 30101104 debug extra
systemd-dbg_229-2_amd64.deb
c89236988e34098d4f64a521e007c550 315850 admin optional
systemd-journal-remote_229-2_amd64.deb
66a6af89c2bd9a096854f118940c9b4d 61742 admin important
systemd-sysv_229-2_amd64.deb
9afccd1cacd1b1c25ee625110c374631 3654292 admin important
systemd_229-2_amd64.deb
6328606aa7865e9175608ba0c16a607d 266906 debian-installer optional
udev-udeb_229-2_amd64.udeb
25188872614e08643a88119c4b9884e8 1039278 admin important udev_229-2_amd64.deb
Package-Type: udeb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBCAAGBQJW02o1AAoJENFO8V2v4RNHYJ8QAIF7s1agXJiLCH3ed41GaNGg
DIWj+zYiFYE4vIKnrKcHkCfzTB5szniJ9WgfDgiPrqjkpFhDNVjkDtzJ14bIIJt5
NG0xQAKo6AbV1MP0vAp39uGC3Ic8Z6MSR2NUfV9/bpMDgW2kn7Mh/Q+SG5HIPSNw
LvNnCR8fG9a6EAeSemjcRn7x05kI4GUh+TIFO1+Y4yJqjm8V1el76mtQl1xLgBz2
jjyZvBJ/s+imi5YhA7Ljk+w+59Slohd15gYFb41s7eqmlJQkOibMpMKA7R72Q3B1
QtNBgKOVAqDjzxE0VGJeYqm4sC+fqmcvloAAS23O/9s2zi8svdUrpcHQw+WmMrJt
uuJbbSEyUFxGtFtPjFjoeAKiSYNYA2ZIHIJqHa8eLyJ9dA+JrW71n7nTIpN1irNi
FXLEWATN61ZkIlLrM3wIKJ/gIQrX+UPvqMQ1Kyd7xilWmjGLrQaHxCsycLMe6x5q
EqOaofjdhuZP4vrrkffwINaEA3vF9RcFqxOYNYeNoyn3708EDRjc4HxVP6dPEELM
73nnkwIN2ZOSTNgGeKc7UQREMkw1a6o08fuEag4FuCiiyT+eGJESikKpOZ6Sz2B4
/I0ya+1svgGdg/kPT44AmnFKsWRmYOU5g5u4I4WgaRV6fsdUUf7SUMFodCJSoCHo
Y0zQipuV8XlZXi5nXdSI
=c5dP
-----END PGP SIGNATURE-----
--- End Message ---
