Your message dated Tue, 3 Jan 2017 10:04:09 +0100
with message-id <20170103090409.ga19...@fatal.se>
and subject line Re: systemd package removal issue
has caused the Debian Bug report #850011,
regarding systemd package removal issue
to be marked as done.
This means that you claim that the problem
Le 01/01/17 à 16:35, Michael Biebl a écrit :
I still don't understand why we would need to move the tmpfiles config
file from systemd to x11-common. Mind you that I don't have any selinux
knowledge.
Afaics, in Debian we have selinux-policy-default which should contain
the selinux policy for the X
On Thu, 22 Dec 2016 14:54:22 +0100 Michael Biebl wrote:
> Am 04.11.2016 um 20:27 schrieb Felipe Sateler:
> > systemd-sysv-install is executed at the client side, not on the server
> > side. This is something that probably makes sense fixing upstream, as
> > units enabled/disabled via the bus are n
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Tue, 2017-01-03 at 13:25 +0100, Michael Biebl wrote:
>
> So, Lennart seems to be not too enthusiastic to add support for running
> systemd-sysv-install on the server side.
>
> Should we add a simple $(id -u) != 0 to systemd-sysv-install then?
>
Package: systemd
Version: 232-8
Severity: normal
When the systemd package is upgraded, the running instance of systemd is
likely to go into 'freezing execution' mode, in which it is unresponsive
to D-Bus requests until the computer is rebooted. If a daemon package is
being upgraded at the same ti
Am 03.01.2017 um 21:05 schrieb Zack Weinberg:
> Package: systemd
> Version: 232-8
> Severity: normal
>
> When the systemd package is upgraded, the running instance of systemd is
> likely to go into 'freezing execution' mode, in which it is unresponsive
This means systemd has crashed for some reas
Am 03.01.2017 um 21:19 schrieb Michael Biebl:
> Am 03.01.2017 um 21:05 schrieb Zack Weinberg:
>> Package: systemd
>> Version: 232-8
>> Severity: normal
>>
>> When the systemd package is upgraded, the running instance of systemd is
>> likely to go into 'freezing execution' mode, in which it is unres
Processing commands for cont...@bugs.debian.org:
> tags 850074 + moreinfo
Bug #850074 [systemd] systemd: "Freezing execution" mode breaks batch upgrades
Added tag(s) moreinfo.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
850074: http://bugs.debian.org/cgi-bin/b
Am 03.01.2017 um 21:41 schrieb Zack Weinberg:
> On Tue, Jan 3, 2017 at 3:19 PM, Michael Biebl wrote:
>>> An ideal fix would be for systemd to support seamless upgrades of itself,
>>> i.e. pid 1 would re-exec itself using the new binary, without losing
>>> any state.
>>
>> Well, that's actually wha
On Tue, Jan 3, 2017 at 3:19 PM, Michael Biebl wrote:
>> An ideal fix would be for systemd to support seamless upgrades of itself,
>> i.e. pid 1 would re-exec itself using the new binary, without losing
>> any state.
>
> Well, that's actually what's already happening. In postinst we run
> systemctl
On Tue, Jan 3, 2017 at 3:55 PM, Michael Biebl wrote:
> Am 03.01.2017 um 21:41 schrieb Zack Weinberg:
>>
>> I don't expect I will be able to reproduce the situation until the
>> next time the systemd package is updated. However, I recall this
>> happening the past several times the systemd package
Control: retitle -1 systemd crashes on daemon-reexec when /run is full
Am 03.01.2017 um 22:25 schrieb Zack Weinberg:
> On Tue, Jan 3, 2017 at 3:55 PM, Michael Biebl wrote:
>> Am 03.01.2017 um 21:41 schrieb Zack Weinberg:
>
>> Hm, yes. It looks like the system (or systemd specifically) was alread
Processing control commands:
> retitle -1 systemd crashes on daemon-reexec when /run is full
Bug #850074 [systemd] systemd: "Freezing execution" mode breaks batch upgrades
Changed Bug title to 'systemd crashes on daemon-reexec when /run is full' from
'systemd: "Freezing execution" mode breaks bat
Processing commands for cont...@bugs.debian.org:
> forwarded 850074 https://github.com/systemd/systemd/issues/5016
Bug #850074 [systemd] systemd crashes on daemon-reexec when /run is full
Set Bug forwarded-to-address to
'https://github.com/systemd/systemd/issues/5016'.
> severity 850074 important
On Tue, Jan 3, 2017 at 4:29 PM, Michael Biebl wrote:
> Aha, thanks a lot for the reproducer. This helps a lot!
>
> Will forward this issue upstream. daemon-reexec should handle the case
> of a full /run more gracefully.
Thanks. When you do that, please also mention that journald doesn't
handle f
Processing commands for cont...@bugs.debian.org:
> tags 850074 = confirmed
Bug #850074 [systemd] systemd crashes on daemon-reexec when /run is full
Added tag(s) confirmed; removed tag(s) moreinfo.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
850074: http://bugs
Am 03.01.2017 um 22:42 schrieb Zack Weinberg:
> On Tue, Jan 3, 2017 at 4:29 PM, Michael Biebl wrote:
>> Aha, thanks a lot for the reproducer. This helps a lot!
>>
>> Will forward this issue upstream. daemon-reexec should handle the case
>> of a full /run more gracefully.
>
> Thanks. When you do
Am 03.01.2017 um 22:46 schrieb Michael Biebl:
> Feel free to file a new issue at
> https://github.com/systemd/systemd/issues/5016
Meant https://github.com/systemd/systemd/issues/new of fcourse
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away fr
Control: severity -1 serious
Control: tags -1 - patch
On 31 December 2016 at 08:30, Francesco Poli wrote:
> On Fri, 30 Dec 2016 22:21:32 +0100 Michael Biebl wrote:
>
>> Am 30.12.2016 um 22:16 schrieb Felipe Sateler:
> [...]
>> > But, your experience appears to uncover
>> > another bug: for some
Processing commands for cont...@bugs.debian.org:
> reassign 850092 adduser
Bug #850092 [udev] addgroup: The group `input' already exists as a system
group. Exiting.
Bug reassigned from package 'udev' to 'adduser'.
No longer marked as found in versions systemd/215-17+deb8u5.
Ignoring request to al
20 matches
Mail list logo
