Processed: [bts-link] source package systemd

2017-10-26 Thread Debian Bug Tracking System
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] source package systemd

2017-10-26 Thread bts-link-upstream
# # 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 # remote status report for #879191 (http://bugs.debian.org/879191) # Bug title: /usr/lib/modprobe.d/systemd.conf

Bug#879603: systemd: network service enters failed state when client goes away too fast

2017-10-26 Thread Julien Cristau
On 10/26/2017 06:10 PM, Michael Biebl wrote: > Control: tags -1 moreinfo > > upstream requested this information at > https://github.com/systemd/systemd/issues/7172#issuecomment-339601311: > > "any chance you can run strace -p1 -s 500 before this, then trigger > this, so that we can see where

Bug#879603: systemd: network service enters failed state when client goes away too fast

2017-10-26 Thread Michael Biebl
Control: tags -1 moreinfo upstream requested this information at https://github.com/systemd/systemd/issues/7172#issuecomment-339601311: "any chance you can run strace -p1 -s 500 before this, then trigger this, so that we can see where precisely the ENOTCONN is generated" -- Why is it that

Processed: Re: Bug#879603: systemd: network service enters failed state when client goes away too fast

2017-10-26 Thread Debian Bug Tracking System
Processing control commands: > tags -1 moreinfo Bug #879603 [systemd] systemd: network service enters failed state when client goes away too fast Added tag(s) moreinfo. -- 879603: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879603 Debian Bug Tracking System Contact ow...@bugs.debian.org