Re: [systemd-devel] [ANNOUNCE] systemd v229

On Mon, 15.02.16 09:36, Umut Tezduyar Lindskog (u...@tezduyar.com) wrote: > >> So, if I define, for example, RuntimeMaxSec=15s, that means unit should > >> stop its job in the interval=[0; 14.59]s and 15.00s will be interval > >> overflow with exit-code 'failure'. OK. But what if unit will stop

Re: [systemd-devel] [ANNOUNCE] systemd v229

Hi, On Fri, Feb 12, 2016 at 10:36 PM, Lennart Poettering wrote: > On Fri, 12.02.16 23:12, Mikhail Kasimov (mikhail.kasi...@gmail.com) wrote: > >> 12.02.2016 22:57, Lennart Poettering пишет: >> > On Fri, 12.02.16 22:28, Mikhail Kasimov (mikhail.kasi...@gmail.com) wrote: >>

Re: [systemd-devel] [ANNOUNCE] systemd v229

On Fri, 12.02.16 23:51, Mikhail Kasimov (mikhail.kasi...@gmail.com) wrote: > > RuntimeMaxSec= just says "abort this shit if it takes longer than > > this". The usecase is to use it for stuff which is not supposed to > > take this long, and where it's better to abort it, and complain than > > to

Re: [systemd-devel] [ANNOUNCE] systemd v229

Dave Reisner wrote on 12/02/16 01:09: > On Thu, Feb 11, 2016 at 10:26:51PM +0100, Reindl Harald wrote: >> >> Am 11.02.2016 um 22:19 schrieb Dave Reisner: >>> On Thu, Feb 11, 2016 at 05:50:08PM +0100, Lennart Poettering wrote: I just tagged the v229 release of systemd. Enjoy! CHANGES

Re: [systemd-devel] [ANNOUNCE] systemd v229

On 12.02.2016 10:54, Colin Guthrie wrote: > Dave Reisner wrote on 12/02/16 01:09: >> On Thu, Feb 11, 2016 at 10:26:51PM +0100, Reindl Harald wrote: >>> >>> Am 11.02.2016 um 22:19 schrieb Dave Reisner: On Thu, Feb 11, 2016 at 05:50:08PM +0100, Lennart Poettering wrote: > I just tagged the

Re: [systemd-devel] [ANNOUNCE] systemd v229

On Fri, Feb 12, 2016 at 10:56:29AM +0100, Armin K. wrote: > On 12.02.2016 10:54, Colin Guthrie wrote: > > Dave Reisner wrote on 12/02/16 01:09: > >> On Thu, Feb 11, 2016 at 10:26:51PM +0100, Reindl Harald wrote: > >>> > >>> Am 11.02.2016 um 22:19 schrieb Dave Reisner: > On Thu, Feb 11, 2016

Re: [systemd-devel] [ANNOUNCE] systemd v229

Armin K. wrote on 12/02/16 09:56: > On 12.02.2016 10:54, Colin Guthrie wrote: >> Dave Reisner wrote on 12/02/16 01:09: >>> On Thu, Feb 11, 2016 at 10:26:51PM +0100, Reindl Harald wrote: Am 11.02.2016 um 22:19 schrieb Dave Reisner: > On Thu, Feb 11, 2016 at 05:50:08PM +0100, Lennart

Re: [systemd-devel] [ANNOUNCE] systemd v229

On Thu, 11.02.16 16:19, Dave Reisner (d...@falconindy.com) wrote: > On Thu, Feb 11, 2016 at 05:50:08PM +0100, Lennart Poettering wrote: > > Heya! > > > > I just tagged the v229 release of systemd. Enjoy! > > > > CHANGES WITH 229: > > > > > > > > * When the stacktrace is extracted

Re: [systemd-devel] [ANNOUNCE] systemd v229

On Thu, 11.02.16 22:26, Reindl Harald (h.rei...@thelounge.net) wrote: > > Am 11.02.2016 um 22:19 schrieb Dave Reisner: > >On Thu, Feb 11, 2016 at 05:50:08PM +0100, Lennart Poettering wrote: > >>I just tagged the v229 release of systemd. Enjoy! > >> > >>CHANGES WITH 229: > >> > >> > >> > >>

Re: [systemd-devel] [ANNOUNCE] systemd v229

On Thu, 11.02.16 19:08, Jóhann B. Guðmundsson (johan...@gmail.com) wrote: > > > On 02/11/2016 05:47 PM, Lennart Poettering wrote: > >On Thu, 11.02.16 17:32, Jóhann B. Guðmundsson (johan...@gmail.com) wrote: > > > >>>I just tagged the v229 release of systemd. Enjoy! > >>> > >>>CHANGES WITH 229:

Re: [systemd-devel] [ANNOUNCE] systemd v229

On Fri, 12.02.16 23:12, Mikhail Kasimov (mikhail.kasi...@gmail.com) wrote: > 12.02.2016 22:57, Lennart Poettering пишет: > > On Fri, 12.02.16 22:28, Mikhail Kasimov (mikhail.kasi...@gmail.com) wrote: > > > >>> TimeoutStopSec= is set to 90s by default. Because it is opt-out and > >>> not opt-in

Re: [systemd-devel] [ANNOUNCE] systemd v229

12.02.2016 22:17, Lennart Poettering пишет: > On Thu, 11.02.16 20:14, Mikhail Kasimov (mikhail.kasi...@gmail.com) wrote: > >> 11.02.2016 19:48, Lennart Poettering пишет: >>> On Thu, 11.02.16 19:47, Mikhail Kasimov (mikhail.kasi...@gmail.com) wrote: >>> 11.02.2016 19:32, Jóhann B. Guðmundsson

Re: [systemd-devel] [ANNOUNCE] systemd v229

On Thu, 11.02.16 19:20, Jan Alexander Steffens (jan.steff...@gmail.com) wrote: > > when i say "start and stop after 20 minutes" i mean stop it not fail > > > > usecase? > > I wanted to say "aborting Type=oneshot services," but that's what > TimeoutStartSec is for. So I was wondering what the

Re: [systemd-devel] [ANNOUNCE] systemd v229

On Fri, 12.02.16 22:28, Mikhail Kasimov (mikhail.kasi...@gmail.com) wrote: > > TimeoutStopSec= is set to 90s by default. Because it is opt-out and > > not opt-in it's set pretty much in all cases. > > > > Note that when the RuntimeMaxSec= timeout hits and systemd starts > > terminating the

Re: [systemd-devel] [ANNOUNCE] systemd v229

On Thu, 11.02.16 20:14, Mikhail Kasimov (mikhail.kasi...@gmail.com) wrote: > 11.02.2016 19:48, Lennart Poettering пишет: > > On Thu, 11.02.16 19:47, Mikhail Kasimov (mikhail.kasi...@gmail.com) wrote: > > > >> 11.02.2016 19:32, Jóhann B. Guðmundsson пишет: > >> > * A new service

Re: [systemd-devel] [ANNOUNCE] systemd v229

12.02.2016 22:57, Lennart Poettering пишет: > On Fri, 12.02.16 22:28, Mikhail Kasimov (mikhail.kasi...@gmail.com) wrote: > >>> TimeoutStopSec= is set to 90s by default. Because it is opt-out and >>> not opt-in it's set pretty much in all cases. >>> >>> Note that when the RuntimeMaxSec= timeout

Re: [systemd-devel] [ANNOUNCE] systemd v229

12.02.2016 23:36, Lennart Poettering пишет: > On Fri, 12.02.16 23:12, Mikhail Kasimov (mikhail.kasi...@gmail.com) wrote: > >> 12.02.2016 22:57, Lennart Poettering пишет: >>> On Fri, 12.02.16 22:28, Mikhail Kasimov (mikhail.kasi...@gmail.com) wrote: >>> > TimeoutStopSec= is set to 90s by

Re: [systemd-devel] [ANNOUNCE] systemd v229

On Thu, 11.02.16 19:03, Reindl Harald (h.rei...@thelounge.net) wrote: > > > Am 11.02.2016 um 17:50 schrieb Lennart Poettering: > > * A new service setting RuntimeMaxSec= has been added that may be > > used > > to specify a maximum runtime for a service. If the timeout is > >

Re: [systemd-devel] [ANNOUNCE] systemd v229

On 02/11/2016 05:47 PM, Lennart Poettering wrote: On Thu, 11.02.16 17:32, Jóhann B. Guðmundsson (johan...@gmail.com) wrote: I just tagged the v229 release of systemd. Enjoy! CHANGES WITH 229: * The coredump collection logic has been reworked: when a coredump is

Re: [systemd-devel] [ANNOUNCE] systemd v229

On Thu, Feb 11, 2016 at 05:50:08PM +0100, Lennart Poettering wrote: > Heya! > > I just tagged the v229 release of systemd. Enjoy! > > CHANGES WITH 229: > > > > * When the stacktrace is extracted from processes of system users, > this > is now done as "systemd-coredump"

Re: [systemd-devel] [ANNOUNCE] systemd v229

On Thu, Feb 11, 2016 at 10:26:51PM +0100, Reindl Harald wrote: > > Am 11.02.2016 um 22:19 schrieb Dave Reisner: > >On Thu, Feb 11, 2016 at 05:50:08PM +0100, Lennart Poettering wrote: > >>I just tagged the v229 release of systemd. Enjoy! > >> > >>CHANGES WITH 229: > >> > >> > >> > >> *

Re: [systemd-devel] [ANNOUNCE] systemd v229

Am 11.02.2016 um 22:19 schrieb Dave Reisner: On Thu, Feb 11, 2016 at 05:50:08PM +0100, Lennart Poettering wrote: I just tagged the v229 release of systemd. Enjoy! CHANGES WITH 229: * When the stacktrace is extracted from processes of system users, this is now done as

[systemd-devel] [ANNOUNCE] systemd v229

Heya! I just tagged the v229 release of systemd. Enjoy! CHANGES WITH 229: * The systemd-resolved DNS resolver service has gained a substantial set of new features, most prominently it may now act as a DNSSEC validating stub resolver. DNSSEC mode is currently turned

Re: [systemd-devel] [ANNOUNCE] systemd v229

Am 11.02.2016 um 17:50 schrieb Lennart Poettering: * A new service setting RuntimeMaxSec= has been added that may be used to specify a maximum runtime for a service. If the timeout is hit, the service is terminated and put into a failure state failure state

Re: [systemd-devel] [ANNOUNCE] systemd v229

Am 11.02.2016 um 18:48 schrieb Lennart Poettering: On Thu, 11.02.16 19:47, Mikhail Kasimov (mikhail.kasi...@gmail.com) wrote: 11.02.2016 19:32, Jóhann B. Guðmundsson пишет: * A new service setting RuntimeMaxSec= has been added that may be used to specify a maximum

Re: [systemd-devel] [ANNOUNCE] systemd v229

On Feb 11, 2016 7:03 PM, "Reindl Harald" wrote: > > > > Am 11.02.2016 um 17:50 schrieb Lennart Poettering: >> >> * A new service setting RuntimeMaxSec= has been added that may be used >>to specify a maximum runtime for a service. If the timeout is hit,

Re: [systemd-devel] [ANNOUNCE] systemd v229

On Thu, 11.02.16 17:32, Jóhann B. Guðmundsson (johan...@gmail.com) wrote: > >I just tagged the v229 release of systemd. Enjoy! > > > >CHANGES WITH 229: > > > > * The coredump collection logic has been reworked: when a coredump > > is > > collected it is now written to disk,

Re: [systemd-devel] [ANNOUNCE] systemd v229

On 02/11/2016 04:50 PM, Lennart Poettering wrote: Heya! I just tagged the v229 release of systemd. Enjoy! CHANGES WITH 229: * The coredump collection logic has been reworked: when a coredump is collected it is now written to disk, compressed and processed

Re: [systemd-devel] [ANNOUNCE] systemd v229

11.02.2016 19:32, Jóhann B. Guðmundsson пишет: >> * A new service setting RuntimeMaxSec= has been added that >> may be used >>to specify a maximum runtime for a service. If the timeout >> is hit, the >>service is terminated and put into a failure state. > > This

Re: [systemd-devel] [ANNOUNCE] systemd v229

On Thu, 11.02.16 19:47, Mikhail Kasimov (mikhail.kasi...@gmail.com) wrote: > 11.02.2016 19:32, Jóhann B. Guðmundsson пишет: > > >> * A new service setting RuntimeMaxSec= has been added that > >> may be used > >>to specify a maximum runtime for a service. If the timeout > >>