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

2016-02-11 Thread Dave Reisner
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: > >> > >> > >> > >> * When

Re: [systemd-devel] [RFC] the chopping block

2016-02-11 Thread Jóhann B . Guðmundsson
On 02/11/2016 09:44 PM, Andrew Bartlett wrote: On Thu, 2016-02-11 at 20:04 +, Jóhann B. Guðmundsson wrote: On 02/11/2016 05:34 PM, Zbigniew Jędrzejewski-Szmek wrote: 2) compat support for libsystemd-login.so and friends (these were merged into a single libsystemd.so a long time ago).

Re: [systemd-devel] [RFC] the chopping block

2016-02-11 Thread Michael Biebl
2016-02-11 18:06 GMT+01:00 Lennart Poettering : > Heya! > > So I am thinking about some spring cleaning, and would love to remove > the following bits from the systemd package: > > 1) systemd-initctl (i.e. the /dev/initctl SysV compat support). Last >time Debian was still using that, maybe this

Re: [systemd-devel] [RFC] the chopping block

2016-02-11 Thread Jóhann B . Guðmundsson
On 02/11/2016 08:41 PM, Armin K. wrote: On 11.02.2016 21:04, Jóhann B. Guðmundsson wrote: On 02/11/2016 05:34 PM, Zbigniew Jędrzejewski-Szmek wrote: 2) compat support for libsystemd-login.so and friends (these were merged into a single libsystemd.so a long time ago). We are still bui

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

2016-02-11 Thread Reindl Harald
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 "sy

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

2016-02-11 Thread Dave Reisner
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" user,

Re: [systemd-devel] [RFC] the chopping block

2016-02-11 Thread Reindl Harald
Am 11.02.2016 um 22:11 schrieb Martin Pitt: Martin Pitt [2016-02-11 21:59 +0100]: This would apply if you boot with systemd, then install sysvinit, and want to reboot the machine (using SysV's /sbin/reboot), right? Or the other way around? This is still somewhat relevant for Debian, but maybe

Re: [systemd-devel] [RFC] the chopping block

2016-02-11 Thread Martin Pitt
Martin Pitt [2016-02-11 21:59 +0100]: > This would apply if you boot with systemd, then install sysvinit, and > want to reboot the machine (using SysV's /sbin/reboot), right? Or the > other way around? > > This is still somewhat relevant for Debian, but maybe there's > something simpler that can b

Re: [systemd-devel] [RFC] the chopping block

2016-02-11 Thread Martin Pitt
Hello, answering for Debian/Ubuntu. Lennart Poettering [2016-02-11 18:06 +0100]: > 1) systemd-initctl (i.e. the /dev/initctl SysV compat support). Last >time Debian was still using that, maybe this changed now? This would apply if you boot with systemd, then install sysvinit, and want to reb

Re: [systemd-devel] [RFC] the chopping block

2016-02-11 Thread Armin K.
On 11.02.2016 21:04, Jóhann B. Guðmundsson wrote: > > > On 02/11/2016 05:34 PM, Zbigniew Jędrzejewski-Szmek wrote: >>> >2) compat support for libsystemd-login.so and friends (these were >>> >merged into a single libsystemd.so a long time ago). We are still >>> >building compat libraries t

Re: [systemd-devel] [RFC] the chopping block

2016-02-11 Thread Reindl Harald
Am 11.02.2016 um 20:37 schrieb Jóhann B. Guðmundsson: Arguably you should chop away the environment files support in the process since you are already wielding the axe... no - damned there are a ton of reasons to use them where it *do not matter* if you would do whatever this way or not th

Re: [systemd-devel] [RFC] the chopping block

2016-02-11 Thread Jóhann B . Guðmundsson
On 02/11/2016 05:34 PM, Zbigniew Jędrzejewski-Szmek wrote: >2) compat support for libsystemd-login.so and friends (these were >merged into a single libsystemd.so a long time ago). We are still >building compat libraries to ease the transition, but that was a >long time ago, hence I'

Re: [systemd-devel] [RFC] the chopping block

2016-02-11 Thread Armin K.
On 11.02.2016 20:44, Zbigniew Jędrzejewski-Szmek wrote: > On Thu, Feb 11, 2016 at 06:45:52PM +0100, Lennart Poettering wrote: >> On Thu, 11.02.16 17:34, Zbigniew Jędrzejewski-Szmek (zbys...@in.waw.pl) >> wrote: >> >>> On Thu, Feb 11, 2016 at 06:06:45PM +0100, Lennart Poettering wrote: Heya! >

Re: [systemd-devel] [RFC] the chopping block

2016-02-11 Thread Zbigniew Jędrzejewski-Szmek
On Thu, Feb 11, 2016 at 06:45:52PM +0100, Lennart Poettering wrote: > On Thu, 11.02.16 17:34, Zbigniew Jędrzejewski-Szmek (zbys...@in.waw.pl) wrote: > > > On Thu, Feb 11, 2016 at 06:06:45PM +0100, Lennart Poettering wrote: > > > Heya! > > > > > > So I am thinking about some spring cleaning, and w

Re: [systemd-devel] [RFC] the chopping block

2016-02-11 Thread Jóhann B . Guðmundsson
On 02/11/2016 05:06 PM, Lennart Poettering wrote: Heya! So I am thinking about some spring cleaning, and would love to remove the following bits from the systemd package: All seem to be very sound choice to make. Arguably you should chop away the environment files support in the process si

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

2016-02-11 Thread Jóhann B . Guðmundsson
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 collected

Re: [systemd-devel] [RFC] the chopping block

2016-02-11 Thread Reindl Harald
Am 11.02.2016 um 19:18 schrieb Matthias Urlichs: On 11.02.2016 18:49, Lennart Poettering wrote: Again: this does not break systems with split off /var, as I tried to make very clear in my original mail. All that's needed is that the initrd mounts /var before handing off control to the main sys

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

2016-02-11 Thread Jan Alexander Steffens
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, the >>servic

Re: [systemd-devel] [RFC] the chopping block

2016-02-11 Thread Matthias Urlichs
On 11.02.2016 18:49, Lennart Poettering wrote: > Again: this does not break systems with split off /var, as I tried to > make very clear in my original mail. All that's needed is that the > initrd mounts /var before handing off control to the main system. I know that. Please don't assume that I mis

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

2016-02-11 Thread Mikhail Kasimov
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 setting RuntimeMaxSec= has been added that may be used to specify a max

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

2016-02-11 Thread Reindl Harald
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 runt

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

2016-02-11 Thread Reindl Harald
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 mak

Re: [systemd-devel] [RFC] the chopping block

2016-02-11 Thread Lennart Poettering
On Thu, 11.02.16 20:57, Andrei Borzenkov (arvidj...@gmail.com) wrote: > 11.02.2016 20:52, Lennart Poettering пишет: > > On Thu, 11.02.16 20:48, Andrei Borzenkov (arvidj...@gmail.com) wrote: > > > >> 11.02.2016 20:06, Lennart Poettering пишет: > >>> > >>> 5) Here's the controversial one I think: s

Re: [systemd-devel] [RFC] the chopping block

2016-02-11 Thread Tom Gundersen
On Thu, Feb 11, 2016 at 6:06 PM, Lennart Poettering wrote: > Heya! > > So I am thinking about some spring cleaning, and would love to remove > the following bits from the systemd package: > All this looks good to me. > 1) systemd-initctl (i.e. the /dev/initctl SysV compat support). Last >t

Re: [systemd-devel] [RFC] the chopping block

2016-02-11 Thread Andrei Borzenkov
11.02.2016 20:52, Lennart Poettering пишет: > On Thu, 11.02.16 20:48, Andrei Borzenkov (arvidj...@gmail.com) wrote: > >> 11.02.2016 20:06, Lennart Poettering пишет: >>> >>> 5) Here's the controversial one I think: support for booting up >>>without /var. We have kludges at quite a few places be

Re: [systemd-devel] [RFC] the chopping block

2016-02-11 Thread Lennart Poettering
On Thu, 11.02.16 20:48, Andrei Borzenkov (arvidj...@gmail.com) wrote: > 11.02.2016 20:06, Lennart Poettering пишет: > > > > 5) Here's the controversial one I think: support for booting up > >without /var. We have kludges at quite a few places because we > >cannot access /var early during

Re: [systemd-devel] [RFC] the chopping block

2016-02-11 Thread Lennart Poettering
On Thu, 11.02.16 18:29, Matthias Urlichs (matth...@urlichs.de) wrote: > Hi, > > Lennart Poettering: > > 5) Here's the controversial one I think: support for booting up > >without /var. > > Meh. I have quite a few multi-boot systems with a common /var/log > partition. Plus, unlike the other "

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

2016-02-11 Thread 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 runtime for a service. If the timeout > >> i

Re: [systemd-devel] [RFC] the chopping block

2016-02-11 Thread Andrei Borzenkov
11.02.2016 20:06, Lennart Poettering пишет: > > 5) Here's the controversial one I think: support for booting up >without /var. We have kludges at quite a few places because we >cannot access /var early during boot. I am tempted to stop >supporting this altogether. Of course, this does

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

2016-02-11 Thread Lennart Poettering
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, comp

Re: [systemd-devel] [RFC] the chopping block

2016-02-11 Thread Matthias Urlichs
Hi, Lennart Poettering: > 5) Here's the controversial one I think: support for booting up >without /var. Meh. I have quite a few multi-boot systems with a common /var/log partition. Plus, unlike the other "spring cleaning" changes this would cause a boot failure after update. Thus: if you mu

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

2016-02-11 Thread Mikhail Kasimov
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 d

Re: [systemd-devel] [RFC] the chopping block

2016-02-11 Thread Lennart Poettering
On Thu, 11.02.16 17:34, Zbigniew Jędrzejewski-Szmek (zbys...@in.waw.pl) wrote: > On Thu, Feb 11, 2016 at 06:06:45PM +0100, Lennart Poettering wrote: > > Heya! > > > > So I am thinking about some spring cleaning, and would love to remove > > the following bits from the systemd package: > > > > 1)

Re: [systemd-devel] [RFC] the chopping block

2016-02-11 Thread Zbigniew Jędrzejewski-Szmek
On Thu, Feb 11, 2016 at 06:06:45PM +0100, Lennart Poettering wrote: > Heya! > > So I am thinking about some spring cleaning, and would love to remove > the following bits from the systemd package: > > 1) systemd-initctl (i.e. the /dev/initctl SysV compat support). Last >time Debian was still

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

2016-02-11 Thread Jóhann B . Guðmundsson
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 (incl

[systemd-devel] [RFC] the chopping block

2016-02-11 Thread Lennart Poettering
Heya! So I am thinking about some spring cleaning, and would love to remove the following bits from the systemd package: 1) systemd-initctl (i.e. the /dev/initctl SysV compat support). Last time Debian was still using that, maybe this changed now? 2) compat support for libsystemd-login.so and

[systemd-devel] [ANNOUNCE] systemd v229

2016-02-11 Thread Lennart Poettering
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 of

Re: [systemd-devel] I want to run systemd inside of a locked down base docker container

2016-02-11 Thread Michal Sekletar
On Thu, Feb 11, 2016 at 2:48 PM, Daniel J Walsh wrote: > I am now masking nothing, just removing /etc/fstab. We will probably > need to back port the dev-hugepages.mount fix > to rhel7 at some point. On RHEL-7.2 dev-hugepages.mount already has ConditionCapability=CAP_SYS_ADMIN. Michal ___

Re: [systemd-devel] I want to run systemd inside of a locked down base docker container

2016-02-11 Thread Daniel J Walsh
On 02/10/2016 05:21 PM, Lennart Poettering wrote: > On Wed, 10.02.16 16:43, Daniel J Walsh (dwa...@redhat.com) wrote: > > I don't see why one would want to mask systemd-logind.service. If you > permit logins and PAM at all, you really need that. If I wanted to add a login program I

Re: [systemd-devel] [HEADS-UP] Preparing for v229

2016-02-11 Thread Michael Biebl
Nvm, seems I had a stray /etc/systemd/system/getty@tty1.service from running systemctl edit --full getty@tty1.service I didn't have that in my pristine test VM with v228 2016-02-11 14:13 GMT+01:00 Michael Biebl : > There seems to be a regression in git master (v228-1303-gcf92d86): > > $ systemct

Re: [systemd-devel] [HEADS-UP] Preparing for v229

2016-02-11 Thread Michael Biebl
There seems to be a regression in git master (v228-1303-gcf92d86): $ systemctl enable getty@tty1.service Failed to execute operation: File exists $ echo $? 1 This didn't fail with v228 2016-02-11 12:00 GMT+01:00 Lennart Poettering : > Heya, > > just wanted to say that v229 is around the corner.

[systemd-devel] [HEADS-UP] Preparing for v229

2016-02-11 Thread Lennart Poettering
Heya, just wanted to say that v229 is around the corner. Maybe later today or tomorrow we'll do the release. If you want to test this before the release, please do so now. Lennart -- Lennart Poettering, Red Hat ___ systemd-devel mailing list systemd-d