> Thanks in advance,
> -Jay
>
> -Original Message-
> From: Lennart Poettering
> Sent: Monday, January 13, 2020 4:33 AM
> To: Burger, Jay
> Cc: [email protected]; Dang, James
> ; Berger, Daniel ;
> Mahabaleshwar, Niranjan
> Subj
, Daniel ;
Mahabaleshwar, Niranjan
Subject: Re: [systemd-devel] Shutdown behavior
On Fr, 10.01.20 10:56, Jay Burger ([email protected]) wrote:
> I made the same type of change in the emergency_action() function in v232.
>
> Question 1: Would this be considered a problem with t
Jay Burger schrieb am 13.01.2020 um 17:36 in
Nachricht <[email protected]>:
...
Personally, I would think the initial shutdown should always be honored.
Unrealistic dramatized example: I have another emergency at Chernobyl
and need to power down my reactor. O
ce fails to start with no log
messages (Ulrich Windl)
--
Message: 1
Date: Mon, 13 Jan 2020 12:18:00 +
From: Dave Howorth
To: [email protected]
Subject: Re: [systemd-devel] Shutdown behavior
Message-ID: <[email protected]>
Content-Type: text/plain; charse
On Mon, 13 Jan 2020 11:32:37 +0100
Lennart Poettering wrote:
> On Fr, 10.01.20 10:56, Jay Burger ([email protected]) wrote:
>
> > I made the same type of change in the emergency_action() function
> > in v232.
> >
> > Question 1: Would this be considered a problem with the design,
> > need
On Fr, 10.01.20 10:56, Jay Burger ([email protected]) wrote:
> I made the same type of change in the emergency_action() function in v232.
>
> Question 1: Would this be considered a problem with the design, needing an
> upstream fix? Or would this be considered a particular user issue, to b
Hi,
I have a couple of questions regarding systemd shutdown behavior.
I first noticed this behavior using systemd v213, I am now on v232
and see the same problem. I found a fix in 213 and patched
the service.c module, in 232 the change needed to move to the
emergency-action.c module.
The problem