Bug#935471: systemd: bogus "Process .. as been marked to be excluded from killing" warning from systemd-shutdown

2019-11-30 Thread Marc Lehmann
On Sat, Nov 30, 2019 at 06:02:17PM +0100, Michael Biebl wrote: > > That's silly and dishonest. > > I guess you just proved the point, thank you. Your point is that when _you_ start throwing around ad-hominems that this is a sign that the _other_ side has stopped being constructive? Is this

Bug#935471: systemd: bogus "Process .. as been marked to be excluded from killing" warning from systemd-shutdown

2019-11-30 Thread Michael Biebl
Am 30.11.19 um 17:56 schrieb Marc Lehmann: > On Sat, Nov 30, 2019 at 04:14:55PM +0100, Michael Biebl > wrote: >> I assume there is no further interest to work collaboratively on this >> from the bug reporters side, so closing the issue. > > Your assumption is wrong, lacks good faith and is

Bug#935471: systemd: bogus "Process .. as been marked to be excluded from killing" warning from systemd-shutdown

2019-11-30 Thread Marc Lehmann
On Sat, Nov 30, 2019 at 04:14:55PM +0100, Michael Biebl wrote: > I assume there is no further interest to work collaboratively on this > from the bug reporters side, so closing the issue. Your assumption is wrong, lacks good faith and is unnecessarily insulting - I provided all information

Bug#935471: systemd: bogus "Process .. as been marked to be excluded from killing" warning from systemd-shutdown

2019-11-11 Thread Marc Lehmann
Hi! All information asked for was either already provided (you even quote the text where it was provided!) or is entirely unnecessary to investigate this problem. I have tried to duplicate the information in a different form below, in case there was a comprehension issue. If you still think some

Bug#935471: systemd: bogus "Process .. as been marked to be excluded from killing" warning from systemd-shutdown

2019-11-11 Thread Michael Biebl
Control: tags -1 + moreinfo Am 23.08.19 um 01:06 schrieb Marc Lehmann: > Package: systemd > Version: 241-5 > Severity: minor > > Dear Maintainer, > > on one of my systems, debian runs from a filesystem image loop-mounted > from an ntfs volume using ntfs-3g, and thus, the ntfs-3g process must be

Processed: Re: Bug#935471: systemd: bogus "Process .. as been marked to be excluded from killing" warning from systemd-shutdown

2019-11-11 Thread Debian Bug Tracking System
Processing control commands: > tags -1 + moreinfo Bug #935471 [systemd] systemd: bogus "Process .. as been marked to be excluded from killing" warning from systemd-shutdown Added tag(s) moreinfo. -- 935471: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935471 Debian Bug Tracking System

Bug#935471: systemd: bogus "Process .. as been marked to be excluded from killing" warning from systemd-shutdown

2019-08-24 Thread Marc Lehmann
On Fri, Aug 23, 2019 at 08:46:12AM +0200, Michael Biebl wrote: > > If you have ideas how to improve the code, a patch would be great. Well, a rather obvious improvement would be to simply remove the code, as it doesn't seem to work (I'm not doing anything fancy other than starting a process

Bug#935471: systemd: bogus "Process .. as been marked to be excluded from killing" warning from systemd-shutdown

2019-08-22 Thread Marc Lehmann
Package: systemd Version: 241-5 Severity: minor Dear Maintainer, on one of my systems, debian runs from a filesystem image loop-mounted from an ntfs volume using ntfs-3g, and thus, the ntfs-3g process must be running at all times, before mounting the root fs and during shutdown. To accomplish