Am Thu, 24 Nov 2016 10:39:52 +0100
schrieb Benoit SCHMID :
> Hello,
>
> On 11/23/2016 03:52 PM, Reindl Harald wrote:
> > so why do you strip the whole context and rest of the response?
> >
> > what is your exactly problem?
> >
> I think my original question on this thread is clear.
> > it shou
On Thu, 24.11.16 10:59, Benoit SCHMID (benoit.sch...@unige.ch) wrote:
> Hello,
>
> On 11/24/2016 12:22 AM, Lennart Poettering wrote:
> > In general, while systemd provides a large degree of SysV compat, in
> > the end we aren't SysV and thus we do not provide 100%. In cases like
> > this this bec
Hello,
On 11/24/2016 12:22 AM, Lennart Poettering wrote:
> In general, while systemd provides a large degree of SysV compat, in
> the end we aren't SysV and thus we do not provide 100%. In cases like
> this this becomes visible.
You are 100% right :-)
Right after upgrading my first server,
I wro
Hello,
On 11/23/2016 03:52 PM, Reindl Harald wrote:
> so why do you strip the whole context and rest of the response?
>
> what is your exactly problem?
>
I think my original question on this thread is clear.
> it should be no rocket science to define a service, order starting as
> needed which en
On Wed, 23.11.16 13:42, Benoit SCHMID (benoit.sch...@unige.ch) wrote:
> Hello,
>
> On 11/23/2016 11:55 AM, Lennart Poettering wrote:
> > The scripts dropped there are executed very late during the shutdown
> > process at a time where all processes have already been killed and all
> > mount points
Am 23.11.2016 um 15:19 schrieb Benoit SCHMID:
On 11/23/2016 03:03 PM, Reindl Harald wrote:
than you need only to adjust "DefaultTimeoutStopSec" to ensure it does
not get killed and order services proper
In most of my tests, this is set to 5min.
Therefore the problem is not located on the fac
Hello,
On 11/23/2016 03:03 PM, Reindl Harald wrote:
> than you need only to adjust "DefaultTimeoutStopSec" to ensure it does
> not get killed and order services proper
In most of my tests, this is set to 5min.
Therefore the problem is not located on the fact that the stop command
ends too early.
Am 23.11.2016 um 13:42 schrieb Benoit SCHMID:
Is there an easy way to create a systemd service that would be stopped
very early
at the shutdown and would avoid the other services stop command to be
executed.
In other world, on my XXX server, the most important service is XXX.
Stopping XXX take
On Wed, Nov 23, 2016 at 3:42 PM, Benoit SCHMID wrote:
> Hello,
>
> On 11/23/2016 11:55 AM, Lennart Poettering wrote:
>> The scripts dropped there are executed very late during the shutdown
>> process at a time where all processes have already been killed and all
>> mount points have been unmounted
Hello,
On 11/23/2016 11:55 AM, Lennart Poettering wrote:
> The scripts dropped there are executed very late during the shutdown
> process at a time where all processes have already been killed and all
> mount points have been unmounted or at least remounted
> read-only.
Is there an easy way to cr
On Wed, 23.11.16 08:18, Benoit SCHMID (benoit.sch...@unige.ch) wrote:
> Hello,
>
> I have added a simple script in /usr/lib/systemd/system-shutdown.
> The scripts echo a message (on stdout) and create a file in /var/tmp.
> I manually tested the script before rebooting to ensure that it
> works fi
Hello,
I have added a simple script in /usr/lib/systemd/system-shutdown.
The scripts echo a message (on stdout) and create a file in /var/tmp.
I manually tested the script before rebooting to ensure that it works fine.
After running init 6, there is no message in journactl -b -1 and the
file has
12 matches
Mail list logo
