Bug#793416: help making systemd drop-in overwrite files take effect
Package: dh-systemd Severity: wishlist Could you please add a feature, so debhelper (dh-systemd) could help making systemd drop-in overwrite files (/lib/systemd/system/unit.service.d/override.conf) take effect? (systemctl daemon-reload + service restart) (guarded by [ -d /run/systemd/system ]) (Override files shipped by different packages.) Cheers, Patrick ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#793374: systemd: Does not honour /etc/systemd/network/*.link
From 14d0625a337511f4ab105c8187c5219abe4e152a Mon Sep 17 00:00:00 2001 From: Julian Wollrath jwollr...@web.de Date: Thu, 23 Jul 2015 14:22:23 +0200 Subject: [PATCH] Copy *.link files from /etc/systemd/network to initramfs The manpage of systemd.link says, that everything in /etc/systemd/network/*.link takes precedence over /lib/systemd/network and others. Hence, the content of /etc/system/network should also be contained in the initramfs, so that this is true. Signed-off-by: Julian Wollrath jwollr...@web.de Closes: #793374 --- debian/extra/initramfs-tools/hooks/udev | 4 1 file changed, 4 insertions(+) diff --git a/debian/extra/initramfs-tools/hooks/udev b/debian/extra/initramfs-tools/hooks/udev index cfe5085ae079..d3d08aa48f93 100755 --- a/debian/extra/initramfs-tools/hooks/udev +++ b/debian/extra/initramfs-tools/hooks/udev @@ -41,6 +41,10 @@ for link in 01-mac-for-usb.link 99-default.link; do fi done +if [ -d /etc/systemd/network/ ]; then + cp -p /etc/systemd/network/*.link $DESTDIR/lib/systemd/network/ +fi + mkdir -p $DESTDIR/lib/udev/rules.d/ for rules in 50-firmware.rules 50-udev-default.rules 60-persistent-storage.rules \ 70-persistent-net.rules 75-net-description.rules 80-net-setup-link.rules \ -- 2.4.6 ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#793374: systemd: Does not honour /etc/systemd/network/*.link
Am 23.07.2015 um 15:09 schrieb Felipe Sateler: On 23 July 2015 at 09:24, Michael Biebl bi...@debian.org wrote: The problem might be, that we don't know, which link files to copy. We will need to check, if it's actually safe to copy all of /etc/systemd/network/*.link into the initramfs. For reference, dracut appears to just copy everything to the initramfs: http://sources.debian.net/src/dracut/040%2B1-1/modules.d/95udev-rules/module-setup.sh/#L47 Thanks for the reference, Felipe. I guess we will just do the same then. -- 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 ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#793374: [PATCH] Copy *.link files from /etc/systemd/network to initramfs
The manpage of systemd.link says, that everything in /etc/systemd/network/*.link takes precedence over /lib/systemd/network and others. Hence, the content of /etc/system/network should also be contained in the initramfs, so that this is true. Signed-off-by: Julian Wollrath jwollr...@web.de Closes: #793374 --- debian/extra/initramfs-tools/hooks/udev | 4 1 file changed, 4 insertions(+) diff --git a/debian/extra/initramfs-tools/hooks/udev b/debian/extra/initramfs-tools/hooks/udev index cfe5085ae079..89cb8d6710a6 100755 --- a/debian/extra/initramfs-tools/hooks/udev +++ b/debian/extra/initramfs-tools/hooks/udev @@ -41,6 +41,10 @@ for link in 01-mac-for-usb.link 99-default.link; do fi done +if `ls /etc/systemd/network/*.link /dev/null 21`; then + cp -p /etc/systemd/network/*.link $DESTDIR/lib/systemd/network/ +fi + mkdir -p $DESTDIR/lib/udev/rules.d/ for rules in 50-firmware.rules 50-udev-default.rules 60-persistent-storage.rules \ 70-persistent-net.rules 75-net-description.rules 80-net-setup-link.rules \ -- 2.4.6 ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#792882: /bin/machinectl: machinectl fails to login to container
Control: merge 771675 -1 This turned out to be the same issue as #771675: missing dbus in the container and missing pts/0 in /etc/securetty Merging the two bug reports. -- 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 ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#793374: systemd: Does not honour /etc/systemd/network/*.link
On 23 July 2015 at 09:24, Michael Biebl bi...@debian.org wrote: The problem might be, that we don't know, which link files to copy. We will need to check, if it's actually safe to copy all of /etc/systemd/network/*.link into the initramfs. For reference, dracut appears to just copy everything to the initramfs: http://sources.debian.net/src/dracut/040%2B1-1/modules.d/95udev-rules/module-setup.sh/#L47 -- Saludos, Felipe Sateler ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#792882: /bin/machinectl: machinectl fails to login to container
Control: tags -1 = upstream Control: severity -1 normal Hi! Am 19.07.2015 um 18:54 schrieb Ritesh Raj Sarraf: Package: systemd Version: 222-2 Severity: important File: /bin/machinectl Tags: patch I am evaluating moving from LXC to systemd-nspawn. During the course, I've run into the following problem, which is known upstream, and claimed to be fixed. My hope was that the fix was part of the 222 release, but I guess that is not the case. The fix: https://github.com/systemd/systemd/commit/f2273101c21bc59a390379e182e53cd4f07a7e71 This commit is part of v222, so there isn't really a patch to cherry-pick (thus removing the patch tag). Can you please file the issue upstream, so this can be dealt with there. Thanks, 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 ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Processed: Re: Bug#792882: /bin/machinectl: machinectl fails to login to container
Processing control commands: forwarded -1 https://github.com/systemd/systemd/issues/685 Bug #792882 [systemd] /bin/machinectl: machinectl fails to login to container Set Bug forwarded-to-address to 'https://github.com/systemd/systemd/issues/685'. -- 792882: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=792882 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#793374: systemd: Does not honour /etc/systemd/network/*.link
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Package: systemd Version: 222-2 Severity: normal Dear Maintainer, I change my network device names via an .link definition in /etc/systemd/network/01-ethernet.link with the following content: [Match] MACAddress=xx:xx:xx:xx:xx:xx OriginalName=eth* Driver=e1000e [Link] Name=eth0 The update to systemd 222-2 broke that. The device gets renamed to enp0s25, disregarding the .link file. A look at the logs shows, that this happens, before the root filesystem is mounted, so when the system is still controlled by the initramfs. The manpage of systemd.link says, that everything in /etc/systemd/network/*.link takes precedence over /lib/systemd/network and others. Hence, the content of /etc/system/network should also be contained in the initramfs, so that this is true. Thank you. With best regards, Julian Wollrath - -- Package-specific info: - -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.1.3 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.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-2 ii libapparmor12.9.2-3 ii libaudit1 1:2.4.2-1 ii libblkid1 2.26.2-6 ii libc6 2.19-19 ii libcap2 1:2.24-9 ii libcap2-bin 1:2.24-9 ii libcryptsetup4 2:1.6.6-5 ii libgcrypt20 1.6.3-2 ii libkmod221-1 ii liblzma55.1.1alpha+20120614-2.1 ii libmount1 2.26.2-6 ii libpam0g1.1.8-3.1 ii libseccomp2 2.2.1-2 ii libselinux1 2.3-2+b1 ii libsystemd0 222-2 ii mount 2.26.2-6 ii sysv-rc 2.88dsf-59.2 ii udev222-2 ii util-linux 2.26.2-6 Versions of packages systemd recommends: ii dbus1.8.20-1 ii libpam-systemd 222-2 Versions of packages systemd suggests: pn systemd-ui none - -- Configuration Files: /etc/systemd/logind.conf changed [not included] /etc/systemd/timesyncd.conf changed [not included] - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQEcBAEBCgAGBQJVsNkTAAoJEFl2dmpRMS8zJ2wIAJhDcm2Nfl6uIZThw9fTvMRj FGXyMnbGjenKNj7baLohtmm3Se/k/gzBoCfvN/xBDxGaoOCfNfZwV9vyq0tD9sLl 7MbKeZ4cZRS9+CmT1oD/sBhH15aGruDJlrZkNFg8jep+cT9Mm7JwTn6vOFRmgAdr ypWuWJoWFMkBEm+71eA3iyjcB8wSx/H8HIA0ZyR/DtCJM5gfdYJHzd21YCpb2QRk 5CTcyu2YMjr+YMbTEEBVs+D31WZkzZ52/2ellxNPwy5EipXcbjG4YnWNtg0G0HnU EfBjuYlGzxU+VYlZyME2PanlK62skdL9dr4Gufk5YnX4Fl6Jqq+64Uqvu49pwdY= =kovn -END PGP SIGNATURE- ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#793374: systemd: Does not honour /etc/systemd/network/*.link
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 The problem probably was introduced in commit 7b5eb265bbb2b in the systemd packaging repo, specifically in this hunk: diff --git a/debian/extra/initramfs-tools/hooks/udev b/debian/extra/initramfs-tools/hooks/udev index beba2eb..9704ef6 100755 - --- a/debian/extra/initramfs-tools/hooks/udev +++ b/debian/extra/initramfs-tools/hooks/udev @@ -32,8 +32,18 @@ cp -a /sbin/udevadm $DESTDIR/sbin/udevadm mkdir -p $DESTDIR/etc/udev cp -p /etc/udev/udev.conf $DESTDIR/etc/udev/ +mkdir -p $DESTDIR/lib/systemd/network/ +for link in 01-mac-for-usb.link 99-default.link; do + if [ -e /etc/systemd/network/$link ]; then + + elif [ -e /lib/systemd/network/$link ]; then +cp -p /lib/systemd/network/$link $DESTDIR/lib/systemd/network/ + fi +done + mkdir -p $DESTDIR/lib/udev/rules.d/ for rules in 50-firmware.rules 50-udev-default.rules 60-persistent-storage.rules \ + 75-net-description.rules 80-net-setup-link.rules \ 61-persistent-storage-android.rules 80-drivers.rules; do if [ -e /etc/udev/rules.d/$rules ]; then cp -p /etc/udev/rules.d/$rules $DESTDIR/lib/udev/rules.d/ As you can see, even if there are files in /etc/systemd/network, they get only copied into the initramfs, if they are named 01-mac-for-usb.link or 99-default.link. You probably want to replace cp -p /etc/systemd/network/$link $DESTDIR/lib/systemd/network/ ^ with cp -p /etc/systemd/network/*.link $DESTDIR/lib/systemd/network/ ^^ With best regards, Julian Wollrath -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQEcBAEBCgAGBQJVsNqvAAoJEFl2dmpRMS8znykH/2IhOkeqsKMHF3ecD99ARFRk 9Lv3yjmZ7G1mDfrQxeRFD0BeY1T/iVy1HUI0BPM/fyZV7vOaBRTXWpTeSrDhB1/Y bEM7KdLCzbALSaRYgMEJMwqJ+gluuMfuJjh2/AsywyDx0YtpDr15Q6/dP+wTkvBi 8mVpotPYtgM2lv2rkH7UDwnYypJi8VNbhV/hE/TLz+n+7u2ahYOIiuTOrqvswqct sVrBaLdwHbDodbiZvaUU/lecEZcpb9fS2tMp7RxXz4GInRdho/wDexmFX5++yFMz f5GtODmUf4+N6LqvVBw3Bmu4FW0hfr0pTMN3c2yfN+ZgL1CdSoAm+WgD84RgkT4= =aUhv -END PGP SIGNATURE- ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Processed: your mail
Processing commands for cont...@bugs.debian.org: tags 793374 + patch Bug #793374 [systemd] systemd: Does not honour /etc/systemd/network/*.link Added tag(s) patch. End of message, stopping processing here. Please contact me if you need assistance. -- 793374: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793374 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#793374: systemd: Does not honour /etc/systemd/network/*.link
Am 23.07.2015 um 14:07 schrieb Julian Wollrath:
Package: systemd
Version: 222-2
Severity: normal
Dear Maintainer,
I change my network device names via an .link definition in
/etc/systemd/network/01-ethernet.link with the following content:
[Match]
MACAddress=xx:xx:xx:xx:xx:xx
OriginalName=eth*
Driver=e1000e
[Link]
Name=eth0
The update to systemd 222-2 broke that. The device gets renamed to
enp0s25, disregarding the .link file. A look at the logs shows, that
this happens, before the root filesystem is mounted, so when the system
is still controlled by the initramfs. The manpage of systemd.link says,
that everything in /etc/systemd/network/*.link takes precedence over
/lib/systemd/network and others. Hence, the content
of /etc/system/network should also be contained in the initramfs, so
that this is true.
The problem might be, that we don't know, which link files to copy.
We will need to check, if it's actually safe to copy all of
/etc/systemd/network/*.link into the initramfs.
For now, I suggest you create a custom hook for your custom configuration like
this:
$ cat /etc/initramfs-tools/hooks/link
#!/bin/sh -e
PREREQS=
case $1 in
prereqs) echo ${PREREQS}; exit 0;;
esac
. /usr/share/initramfs-tools/hook-functions
mkdir -p $DESTDIR/lib/systemd/network/
cp -p /etc/systemd/network/01-ethernet.link $DESTDIR/lib/systemd/network/
Then make the script executable and run update-initramfs -u
Regards,
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
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#793374: systemd: Does not honour /etc/systemd/network/*.link
+if [ -d /etc/systemd/network/ ]; then + cp -p /etc/systemd/network/*.link $DESTDIR/lib/systemd/network/ +fi This could break update-initramfs if no *.link files in /etc/systemd/network exist. The new version of the patch, which I already send out, adjusts the check, so that that does not happen. ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Processed: forcibly merging 771675 792882
Processing commands for cont...@bugs.debian.org: forcemerge 771675 792882 Bug #771675 [systemd] systemd: machinectl: Failed to get container bus: Input/output error Bug #771675 [systemd] systemd: machinectl: Failed to get container bus: Input/output error Marked as found in versions systemd/222-2. Added tag(s) upstream. Bug #792882 [systemd] /bin/machinectl: machinectl fails to login to container Unset Bug forwarded-to-address Severity set to 'minor' from 'normal' Marked as found in versions systemd/215-7. Merged 771675 792882 thanks Stopping processing here. Please contact me if you need assistance. -- 771675: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771675 792882: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=792882 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#793198: systemd: poweroff, reboot without stopping services and unmounting
Please help write shutdown log. Method described here doesn't work: https://wiki.freedesktop.org/www/Software/systemd/Debugging/#diagnosingshutdownproblems boot with the debug options: systemd.log_level=debug systemd.log_target=kmsg log_buf_len=1M enforcing=0 save the following script as /usr/lib/systemd/system-shutdown/debug.sh and make it executable: #!/bin/sh mount -o remount,rw / dmesg /shutdown-log.txt mount -o remount,ro / chmod a+x /usr/lib/systemd/system-shutdown/debug.sh No /shutdown-log.txt is created. ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#793416: help making systemd drop-in overwrite files take effect
On 23 July 2015 at 17:28, Patrick Schleizer adrela...@riseup.net wrote: Package: dh-systemd Severity: wishlist Could you please add a feature, so debhelper (dh-systemd) could help making systemd drop-in overwrite files (/lib/systemd/system/unit.service.d/override.conf) take effect? (systemctl daemon-reload + service restart) (guarded by [ -d /run/systemd/system ]) (Override files shipped by different packages.) I'm not sure a package should restart anothe service. Is there precedent for this? I seem to recall libc or libssl asking me which services I should restart, but I don't remember ever seeing any packages restart other services. -- Saludos, Felipe Sateler ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#792187: systemd: systemctl start not working when ReadWriteDirectories is a symlink
Hm, if the Chromium kernel/LSM forbids this, I don't see how this can be fixed in systemd? Do you? Obviously the answer is no... i reported here since the commands in the service file were working fine when executed by hand, so i thought it couldn't be a kernel issue, but how systemd handled this kernel restricion. Maybe could systemd handle such an issue transparently? Thanks. ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
subscribe
subscribe ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#787480: build with iptables support
On 23 July 2015 at 12:32, Michael Biebl bi...@debian.org wrote: Am 23.07.2015 um 13:21 schrieb Dimitri John Ledkov: If we in-vision that networkd is / will-be required on minimal systems, I would want to have an alternative build available of networkd nspawn with firewall support enabled. (could be something like update-alternatives, or e.g. systemd-networkd-firewall.service that conflicts with normal networkd units or whatever.) I think it would be highly confusing to have two builds of systemd-networkd with different feature sets and bringing update-alternatives into the mix wouldn't help. So I'm not sure we want this. So split networkd into stand-alone package, and enable iptables-dev dependency. It's not enabled by default service, is it? Thus should not be installed together with init, given the deps it wants / pulls in. And from the bug reports there is clearly demand for full functionality to be available from networkd. Looks like win-win, minimal install is kept minimal, yet optional component is fully featured. -- Regards, Dimitri. ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#793374: systemd: Does not honour /etc/systemd/network/*.link
Am 23.07.2015 um 14:25 schrieb Julian Wollrath: diff --git a/debian/extra/initramfs-tools/hooks/udev b/debian/extra/initramfs-tools/hooks/udev index cfe5085ae079..d3d08aa48f93 100755 --- a/debian/extra/initramfs-tools/hooks/udev +++ b/debian/extra/initramfs-tools/hooks/udev @@ -41,6 +41,10 @@ for link in 01-mac-for-usb.link 99-default.link; do fi done +if [ -d /etc/systemd/network/ ]; then + cp -p /etc/systemd/network/*.link $DESTDIR/lib/systemd/network/ +fi + I don't think there is a good reason to copy the 01-mac-for-usb.link 99-default.link files twice. If we are going to copy all *.link files, the preceding section should be removed -- 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 ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#793374: systemd: Does not honour /etc/systemd/network/*.link
Am 23.07.2015 um 14:07 schrieb Julian Wollrath: Package: systemd Version: 222-2 Severity: normal Dear Maintainer, I change my network device names via an .link definition in /etc/systemd/network/01-ethernet.link with the following content: [Match] MACAddress=xx:xx:xx:xx:xx:xx OriginalName=eth* Driver=e1000e [Link] Name=eth0 The update to systemd 222-2 broke that. The device gets renamed to enp0s25, disregarding the .link file. A look at the logs shows, that this happens, before the root filesystem is mounted, so when the system is still controlled by the initramfs. The manpage of systemd.link says, that everything in /etc/systemd/network/*.link takes precedence over /lib/systemd/network and others. Hence, the content of /etc/system/network should also be contained in the initramfs, so that this is true. As a related remark, we already have the same problem if users rename their interfaces via udev rules and they don't use /etc/udev/rules.d/70-persistent-net.rules but create a custom rules file for that. -- 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 ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Processed: [bts-link] source package systemd
Processing commands for cont...@bugs.debian.org: # # bts-link upstream status pull for source package systemd # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user bts-link-upstr...@lists.alioth.debian.org Setting user to bts-link-upstr...@lists.alioth.debian.org (was bts-link-de...@lists.alioth.debian.org). # remote status report for #792403 (http://bugs.debian.org/792403) # Bug title: systemd-bootchart crashes when writing the svg # * https://github.com/systemd/systemd/issues/583 # * remote status changed: open - closed # * closed upstream tags 792403 + fixed-upstream Bug #792403 [systemd] systemd-bootchart crashes when writing the svg Added tag(s) fixed-upstream. usertags 792403 - status-open Usertags were: status-open. Usertags are now: . usertags 792403 + status-closed There were no usertags set. Usertags are now: status-closed. thanks Stopping processing here. Please contact me if you need assistance. -- 792403: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=792403 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#793372: systemd breaks LXC cgroup memory limitations
Package: systemd Version: 215-17+deb8u1 Severity: important Dear Maintainer, I have been checking on LXC for a while. I wanted to acquaint with the containers management, specifically with the resources limitation capabilities. I have created, configured and destroyed several containers. The issue comes when I try to limit the memory usage. I have added this option to the grub defaults: cgroup_enable=memory This allowed me to start a container with options configured such as this: lxc.cgroup.memory.limit_in_bytes = 1024M lxc.cgroup.memory.memsw.limit_in_bytes = 1200M The thing is that when I try to use more than 1200 MB of memory, inside the container, I actually can. I have used a very simply script I found on someone page to test the memory allocation capabilities. memory_allocation.py #!/usr/bin/env python import sys import time if len(sys.argv) != 2: print usage: fillmem number-of-megabytes sys.exit() count = int(sys.argv[1]) megabyte = (0,) * (1024 * 1024 / 8) data = megabyte * count while True: time.sleep(1) I have tried to isolate the problem, focusing on some missing LXC or cgroups configuration. Let me add the trace: First, I have created a new control group, outside the LXC stuff: cgcreate -g memory:/bmalloc1gb echo $(( 1024 * 1024 * 1024 ))|tee /sys/fs/cgroup/memory/bmalloc1gb/memory.limit_in_bytes echo $(( 1200 * 1024 * 1024 ))|tee /sys/fs/cgroup/memory/bmalloc1gb/memory.memsw.limit_in_bytes cgexec -g memory:/bmalloc1gb bash python memory_allocation.py 2000 [killed] When I run the script on this environment, the memory allocation did not went far from this 1200 MB, which is what I need. Second, I have joined the LXC cgroup, to try the very same as above: cgexec -g memory:lxc/test bash python memory_allocation.py 2000 [killed] This two tests made me point to LXC, but after some internet digging I found this: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777601 In this bug report, which is not exactly the same as this one, the reporter states this: I also tested something which may be another problem (so another ticket) but the memory and swap limitation doesn't work at all :-(...with or without this bug. I can't tell if it's linked or not. I tested cpu pinning and it works like a charm. The issue seems related to memory and swap only. After this income information, I have switched back both the host and the container, to sysvinit. With the systems booted on sysvinit, the memory limitation is working as it is expected. Let me add the whole container configuration for your reference: lxc.cgroup.cpuset.cpus = 0,1 lxc.cgroup.cpu.shares = 256 lxc.cgroup.blkio.weight = 500 lxc.cgroup.memory.limit_in_bytes = 1024M lxc.cgroup.memory.memsw.limit_in_bytes = 1200M lxc.network.type = veth lxc.network.flags = up lxc.network.link = br0 lxc.network.name = eth0 lxc.rootfs = /dev/vg/test lxc.start.auto = 1 lxc.include = /usr/share/lxc/config/debian.common.conf lxc.mount = /var/lib/lxc/test/fstab lxc.utsname = test lxc.arch = amd64 lxc.autodev = 1 Thanks for your consideration. Best regards. -- Package-specific info: -- System Information: Debian Release: 8.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.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 acl 2.2.52-2 ii adduser 3.113+nmu3 ii initscripts 2.88dsf-59 ii libacl1 2.2.52-2 ii libaudit1 1:2.4-1+b1 ii libblkid1 2.25.2-6 ii libc6 2.19-18 ii libcap2 1:2.24-8 ii libcap2-bin 1:2.24-8 ii libcryptsetup4 2:1.6.6-5 ii libgcrypt20 1.6.3-2 ii libkmod218-3 ii liblzma55.1.1alpha+20120614-2+b3 ii libpam0g1.1.8-3.1 ii libselinux1 2.3-2 ii libsystemd0 215-17+deb8u1 ii mount 2.25.2-6 ii sysv-rc 2.88dsf-59 ii udev215-17+deb8u1 ii util-linux 2.25.2-6 Versions of packages systemd recommends: ii dbus1.8.18-0+deb8u1 ii libpam-systemd 215-17+deb8u1 Versions of packages systemd suggests: pn systemd-ui none -- no debconf information ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#792882: /bin/machinectl: machinectl fails to login to container
I've filed the bug upstream at: https://github.com/systemd/systemd/issues/685 On Thu, Jul 23, 2015 at 5:22 PM, Michael Biebl bi...@debian.org wrote: Am 23.07.2015 um 13:48 schrieb Michael Biebl: I am evaluating moving from LXC to systemd-nspawn. During the course, I've run into the following problem, which is known upstream, and claimed to be fixed. My hope was that the fix was part of the 222 release, but I guess that is not the case. The fix: https://github.com/systemd/systemd/commit/f2273101c21bc59a390379e182e53cd4f07a7e71 This commit is part of v222, so there isn't really a patch to cherry-pick (thus removing the patch tag). Can you please file the issue upstream, so this can be dealt with there. Not quite sure if [1] is related, but I suggest you look at that existing bug report as well. Maybe it contains some hints. Michael [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771675 -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? -- Ritesh Raj Sarraf RESEARCHUT - http://www.researchut.com Necessity is the mother of invention. ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#793374: systemd: Does not honour /etc/systemd/network/*.link
On Thu, 23 Jul 2015 14:07:36 +0200 Julian Wollrath jwollr...@web.de wrote: I change my network device names via an .link definition in /etc/systemd/network/01-ethernet.link with the following content: [Match] MACAddress=xx:xx:xx:xx:xx:xx OriginalName=eth* Driver=e1000e [Link] Name=eth0 Doesn't systemd (networkd/udev) specifically disallow renaming to eth*, and force renaming to something that can't conflict with a kernel-assigned device name instead? Does this work if you rename to, say, foo0? - Josh Triplett ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#792922: Solved
Solution: I've created a new default cupsd.conf file. That strange behavior no longer exists. Until 2 weeks ago there had been needed only that Listen entry: Listen /var/run/cups/cups.sock Now to work correctly 2 lines are needed: Listen localhost:631 Listen /var/run/cups/cups.sock Bug can be closed. -- Thanks, Andreas ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#793366: systemd: please enable iptables support
Package: systemd Severity: normal Version: 222-2 Please add iptables-dev build-dependency and thus enable libiptc which in turn should enable systemd-networkd IPMasquarade support as well as NAT in nspawn. Regards, Dimitri. ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#793366: systemd: please enable iptables support
Control: forcemerge 787480 -1 Hi Dimitri, Am 23.07.2015 um 12:33 schrieb Dimitri John Ledkov: Package: systemd Severity: normal Version: 222-2 Please add iptables-dev build-dependency and thus enable libiptc which in turn should enable systemd-networkd IPMasquarade support as well as NAT in nspawn. This is a duplicate of https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787480 See the bug report, why this feature hasn't been enabled yet. -- 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 ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Processed: Re: Bug#793366: systemd: please enable iptables support
Processing control commands: forcemerge 787480 -1 Bug #787480 [systemd] build with iptables support Bug #793366 [systemd] systemd: please enable iptables support Marked as found in versions systemd/220-3. Bug #787480 [systemd] build with iptables support Marked as found in versions systemd/222-2. Merged 787480 793366 -- 787480: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787480 793366: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793366 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
