[systemd-devel] Configuring wakeup-online at runtime with networkctl

Hello, I would like to know if it's possible to configure an interface at runtime to enable wol without rebooting my machine. I tried to create a link file that has WakeOnLan=magic and did 'networkctl reconfigure ens0' but it doesn't work. Also is it possible to display the status of wakeup

Re: [systemd-devel] network config breaks when starting a nspawn container

On Thu, Jan 27, 2022 at 7:26 AM Francis Moreau wrote: > > Hi, > > systemd-networkd creates a bridge 'br0': > > $ cat /etc/systemd/network/30-br0.network > [Match] > Name=br0 > > [Network] > DHCP=ipv4 > Domains=~. > > The bridge has one slave '

[systemd-devel] network config breaks when starting a nspawn container

Hi, systemd-networkd creates a bridge 'br0': $ cat /etc/systemd/network/30-br0.network [Match] Name=br0 [Network] DHCP=ipv4 Domains=~. The bridge has one slave 'bond0' by default. The bond device is used to aggregate my ethernet card and my wifi card (configured by NM). systemd-resolved is

[systemd-devel] Why does sd_path_lookup(SD_PATH_TMPFILES, ..) return one path ?

Hello, I was expecting that this function returns all paths where tmpfiles can be stored but it returns only "/usr/lib/tmpfiles.d". Why doesn't it return also "/etc/tmpfiles.d" ? Thanks you -- Francis

Re: [systemd-devel] How to restart my socket activated service safely ?

On Tue, Jul 27, 2021 at 11:12 AM Mantas Mikulėnas wrote: > > On Tue, Jul 27, 2021 at 10:10 AM Francis Moreau > wrote: > > > > Hello, > > > > During my application update, I want to restart my service which is > > activated by a socket but want to be sure

[systemd-devel] How to restart my socket activated service safely ?

Hello, During my application update, I want to restart my service which is activated by a socket but want to be sure that no request sent to my service will be missed. I also want to restart the socket too so systemd uses the latest version of the socket unit file. If I restart the socket when

Re: [systemd-devel] How can I simply check that a service has been restarted ?

On Tue, Nov 10, 2020 at 6:35 PM Luca Boccassi wrote: > > On Tue, 2020-11-10 at 17:22 +, Luca Boccassi wrote: > > On Tue, 2020-11-10 at 18:12 +0100, Francis Moreau wrote: > > > On Tue, Nov 10, 2020 at 2:43 PM Luca Boccassi wrote: > > > > On Tue, 2020-11-10 at

Re: [systemd-devel] How can I simply check that a service has been restarted ?

On Tue, Nov 10, 2020 at 2:43 PM Luca Boccassi wrote: > > On Tue, 2020-11-10 at 11:50 +0100, Francis Moreau wrote: > > On Tue, Nov 10, 2020 at 11:30 AM Lennart Poettering > > wrote: > > > On Di, 10.11.20 10:28, Francis Moreau (francis.m...@gmail.com)

Re: [systemd-devel] How can I simply check that a service has been restarted ?

I hope that helps. Thank you however I don't control the type of the restarted units, it can be anything, > > > On Tue, Nov 10, 2020 at 11:50 AM Francis Moreau > wrote: >> >> On Tue, Nov 10, 2020 at 11:30 AM Lennart Poettering >> wrote: >> > >>

Re: [systemd-devel] How can I simply check that a service has been restarted ?

On Tue, Nov 10, 2020 at 11:30 AM Lennart Poettering wrote: > > On Di, 10.11.20 10:28, Francis Moreau (francis.m...@gmail.com) wrote: > > > Hello, > > > > After restarting a service with "systemctl try-restart ..." I want to > > verify that the se

[systemd-devel] How can I simply check that a service has been restarted ?

Hello, After restarting a service with "systemctl try-restart ..." I want to verify that the service has been restarted. How can I reliably do this without using the dbus API ? Thank you -- Francis ___ systemd-devel mailing list

Re: [systemd-devel] 99-default.link which such a high number ?

On Fri, Sep 25, 2020 at 4:59 PM Mantas Mikulėnas wrote: > > On Fri, Sep 25, 2020, 17:46 Francis Moreau wrote: >> >> Hello, >> >> I want to override /usr/lib/systemd/network/99-default.link so I need >> to create a file starting with "99-" prefix.

Re: [systemd-devel] 99-default.link which such a high number ?

On Fri, Sep 25, 2020 at 4:59 PM Mike Gilbert wrote: > > On Fri, Sep 25, 2020 at 10:46 AM Francis Moreau > wrote: > > > > Hello, > > > > I want to override /usr/lib/systemd/network/99-default.link so I need > > to create a file starting with "99-"

[systemd-devel] 99-default.link which such a high number ?

Hello, I want to override /usr/lib/systemd/network/99-default.link so I need to create a file starting with "99-" prefix. This doesn't seem logical to me because the numbers are supposed to encode the priority however nothing is left to the user if the defaults used is 99. I find more logical

Re: [systemd-devel] Why systemd keeps references on passed sockets ?

On Tue, Sep 8, 2020 at 5:41 PM Lennart Poettering wrote: > > On Di, 08.09.20 17:35, Francis Moreau (francis.m...@gmail.com) wrote: > > > On Mon, Sep 7, 2020 at 4:38 PM Lennart Poettering > > wrote: > > > > > > "React on the socket close?" — Wha

Re: [systemd-devel] Why systemd keeps references on passed sockets ?

On Mon, Sep 7, 2020 at 4:38 PM Lennart Poettering wrote: > > "React on the socket close?" — What do you mean by that? > I mean if my service explicitly calls close() then systemd could stop the socket on its side so its are freed until the service is restarted. I think it is what you described

Re: [systemd-devel] Why systemd keeps references on passed sockets ?

On Sat, Sep 5, 2020 at 12:18 AM Lennart Poettering wrote: > > On Fr, 04.09.20 21:53, Francis Moreau (francis.m...@gmail.com) wrote: > > > Hi, > > > > I have a service which is activated by a socket unit. When systemd > > passes the (netlink) socket to my ser

[systemd-devel] Why systemd keeps references on passed sockets ?

Hi, I have a service which is activated by a socket unit. When systemd passes the (netlink) socket to my service it seems that it still keeps a reference on the socket, at least ss(8) showed this. Is this expected ? If yes can this be prevented ? I'm asking because my service may not need the

Re: [systemd-devel] No DHCP server is started with DHCPServer=yes

On Wed, May 6, 2020 at 11:47 PM Lennart Poettering wrote: > > On Mi, 06.05.20 23:43, Francis Moreau (francis.m...@gmail.com) wrote: > > > Hi, > > > > I'm running systemd v245 (in the host and in the containers) and I > > have 2 containers whose veth link is c

[systemd-devel] No DHCP server is started with DHCPServer=yes

Hi, I'm running systemd v245 (in the host and in the containers) and I have 2 containers whose veth link is connected to a bridge. One container named "c1" uses "DHCPServer=yes" and is supposed to provide an ipv4 address to the second container "c2" but for some reasons it seems that no DHCP

Re: [systemd-devel] Backup the current boot logs in raw format

On Thu, Aug 1, 2019 at 10:36 AM Zbigniew Jędrzejewski-Szmek wrote: > > On Thu, Aug 01, 2019 at 10:26:50AM +0200, Francis Moreau wrote: > > On Thu, Aug 1, 2019 at 9:45 AM Zbigniew Jędrzejewski-Szmek > > wrote: > > > > > > On Thu, Aug 01, 2019 at 09

Re: [systemd-devel] Backup the current boot logs in raw format

On Thu, Aug 1, 2019 at 9:45 AM Zbigniew Jędrzejewski-Szmek wrote: > > On Thu, Aug 01, 2019 at 09:11:19AM +0200, Francis Moreau wrote: > > On Wed, Jul 24, 2019 at 4:08 PM Zbigniew Jędrzejewski-Szmek > > wrote: > > > you can export and write to a journal file with: &

Re: [systemd-devel] Backup the current boot logs in raw format

On Wed, Jul 24, 2019 at 4:08 PM Zbigniew Jędrzejewski-Szmek wrote: > you can export and write to a journal file with: > journalctl -o export ... | /usr/lib/systemd/systemd-journal-remote -o > /tmp/foo.journal - > This has the advantage that you can apply any journalctl filter where > the dots

Re: [systemd-devel] Backup the current boot logs in raw format

On Wed, Jul 24, 2019 at 4:08 PM Zbigniew Jędrzejewski-Szmek wrote: > journalctl -o export ... | /usr/lib/systemd/systemd-journal-remote -o > /tmp/foo.journal - > This has the advantage that you can apply any journalctl filter where > the dots are, e.g. '-b'. Thanks ! It's documented in man

[systemd-devel] Backup the current boot logs in raw format

Hi, I would like to backup the journal logs for the current boot in a "raw" format so I can reuse it later with "journalctl --file=my-backup". But looking at the different values for "-o" option I can't find the answer. Could anybody give me some clues ? Thanks. -- Francis

Re: [systemd-devel] Question about the default value of NamePolicy=

Hello, On Wed, Aug 1, 2018 at 7:36 PM, Mantas Mikulėnas wrote: > > AFAIK, "onboard" and (hotplug) "slot" names are mutually exclusive, so their > relative ordering isn't that important... but if the firmware marks a device > as on-board *and* also provides a slot number, then it's more likely

[systemd-devel] Question about the default value of NamePolicy=

Hello, I have a question regarding the default value of NamePolicy= defined in 99-default.link. The value is "NamePolicy=kernel database onboard slot path" Could someone explain me why "onbard" is preferred over "slot" which is preferred over "path" ? Thanks. -- Francis

[systemd-devel] .network has [Link] and there's already .link

Hello, I dont understand .network has [Link] section whereas network device configuration can also done with .link file. It seems that there's a overlap... what is the rational here ? Thank you in advance. -- Francis ___ systemd-devel mailing list

[systemd-devel] Why "systemctl -H " instead of "ssh -- systemctl"

Hello, I'm wondering why systemctl has the -H option whereas one can achieve the same by calling "ssh -- systemctl ...". Thanks. -- Francis ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org

Re: [systemd-devel] What is the recommended way to setup the compose key ?

On Tue, Nov 28, 2017 at 9:57 AM, Mantas Mikulėnas wrote: > > And where would it get the actual compose definitions from? They have to be > defined in the keymap itself. > on my distro (opensuse Tumbleweed) compose tables and the definition of the compose key can be found

Re: [systemd-devel] What is the recommended way to setup the compose key ?

On Tue, Nov 28, 2017 at 9:46 AM, Mantas Mikulėnas <graw...@gmail.com> wrote: > On Tue, Nov 28, 2017 at 10:35 AM, Francis Moreau <francis.m...@gmail.com> > wrote: >> >> Hello, >> >> I'm trying to figure out how I can configure a compose key for the &g

[systemd-devel] What is the recommended way to setup the compose key ?

Hello, I'm trying to figure out how I can configure a compose key for the consoles. I looked at man localectl and vconsole.conf but haven't found an answer. Could anybody give me some hints ? Thanks. -- Francis ___ systemd-devel mailing list

Re: [systemd-devel] Question about systemd-firstboot

On Thu, Mar 9, 2017 at 5:49 PM, Zbigniew Jędrzejewski-Szmek wrote: >> So if 'ro' is used, systemd-firstboot is not working. If it's expected >> I think it would worth a note in the documentation. > It's supposed to work, I think. Please open an issue, it'll be better > tracked

Re: [systemd-devel] Question about systemd-firstboot

On Thu, Mar 9, 2017 at 5:19 PM, Zbigniew Jędrzejewski-Szmek wrote: > It depends on the command-line parameters: 'ro' and 'rw' both work. > 'rw' is actually recommended if you're using an initramfs. > who is recommending 'rw' ? do you have any pointers ? > Otherwise, an empty

Re: [systemd-devel] Question about systemd-firstboot

On Thu, Mar 9, 2017 at 3:10 PM, Zbigniew Jędrzejewski-Szmek <zbys...@in.waw.pl> wrote: > On Thu, Mar 09, 2017 at 10:48:03AM +0100, Francis Moreau wrote: >> Hello, >> >> I'm puzzled about systemd-firstboot service. >> >> In my understanding this s

[systemd-devel] Question about systemd-firstboot

Hello, I'm puzzled about systemd-firstboot service. In my understanding this service is ran only during the firstboot. The firstboot condition is detected with the presence of /etc/machine-id file. If this file is not present then it's assumed to be a first boot and systemd-firstboot.service is

Re: [systemd-devel] sysv-generator weirdness for shutdown runlevels

On Thu, May 26, 2016 at 8:15 AM, Andrei Borzenkov <arvidj...@gmail.com> wrote: > On Thu, May 26, 2016 at 8:49 AM, Francis Moreau <francis.m...@gmail.com> > wrote: >> >> So let's take an example. Please note that I'm really not sure what's >> the expected beha

Re: [systemd-devel] sysv-generator weirdness for shutdown runlevels

Hello Michael, On Wed, May 25, 2016 at 11:08 PM, Michael Biebl wrote: > Hm, I've already given you the answer on IRC, so I'm not sure why you > ask them again. > Indee and thank you for that. But you also told me that /etc/init.d/rc0.d isn't supported by Debian, and my

[systemd-devel] sysv-generator weirdness for shutdown runlevels

Hello, I'm starring at a chunk of code of the sysv-generator (shown below) for some while now and I still can't see its purpose. Here's the code taken from src/sysv-generator/sysv-generator.c: static int set_dependencies_from_rcnd(const LookupPaths *lp, Hashmap *all_services) { [...]

Re: [systemd-devel] Why does sysv generator translate Required-Start keyword into an After= ordering dep only ?

On Tue, Mar 8, 2016 at 10:19 AM, Andrei Borzenkov <arvidj...@gmail.com> wrote: > 08.03.2016 11:33, Francis Moreau пишет: >> On Tue, Mar 8, 2016 at 9:23 AM, Andrei Borzenkov <arvidj...@gmail.com> wrote: >>> 08.03.2016 11:07, Francis Moreau пишет: >>>&

Re: [systemd-devel] Why does sysv generator translate Required-Start keyword into an After= ordering dep only ?

On Tue, Mar 8, 2016 at 9:23 AM, Andrei Borzenkov <arvidj...@gmail.com> wrote: > 08.03.2016 11:07, Francis Moreau пишет: >> On Tue, Mar 8, 2016 at 7:51 AM, Andrei Borzenkov <arvidj...@gmail.com> wrote: >>> 07.03.2016 10:04, Francis Moreau пишет: >>>>

Re: [systemd-devel] Why does sysv generator translate Required-Start keyword into an After= ordering dep only ?

On Tue, Mar 8, 2016 at 7:51 AM, Andrei Borzenkov <arvidj...@gmail.com> wrote: > 07.03.2016 10:04, Francis Moreau пишет: >> Hello, >> >> Sorry for the long delay. >> >> On Fri, Feb 26, 2016 at 5:05 AM, Andrei Borzenkov <arvidj...@gmail.com> >>

Re: [systemd-devel] Why does sysv generator translate Required-Start keyword into an After= ordering dep only ?

On Mon, Mar 7, 2016 at 2:13 PM, Lukáš Nykrýn <lnyk...@redhat.com> wrote: > Francis Moreau píše v Po 07. 03. 2016 v 08:04 +0100: >> Hello, >> >> Sorry for the long delay. >> >> On Fri, Feb 26, 2016 at 5:05 AM, Andrei Borzenkov < >> arvidj...@gmail.c

Re: [systemd-devel] Why does sysv generator translate Required-Start keyword into an After= ordering dep only ?

Hello, Sorry for the long delay. On Fri, Feb 26, 2016 at 5:05 AM, Andrei Borzenkov <arvidj...@gmail.com> wrote: > 26.02.2016 00:55, Francis Moreau пишет: >> >> But now I'm wondering how the following case is handled: a sysinit >> script "a" has "Requi

Re: [systemd-devel] Why does sysv generator translate Required-Start keyword into an After= ordering dep only ?

On Wed, Feb 24, 2016 at 6:12 PM, Lennart Poettering <lenn...@poettering.net> wrote: > On Wed, 24.02.16 17:40, Francis Moreau (francis.m...@gmail.com) wrote: > >> Hello, >> >> It seems that the unit generator for sysv init scripts translate >> "Required-Star

[systemd-devel] Why does sysv generator translate Required-Start keyword into an After= ordering dep only ?

Hello, It seems that the unit generator for sysv init scripts translate "Required-Start: X" into "After=X" native ordering deps only. I would also have expected it to add the following dependency "Requires=X" too. What am I missing ? Thanks. -- Francis

Re: [systemd-devel] umounting FS happens to be at the same time as shutting down services

On Sun, Nov 22, 2015 at 4:04 PM, Lennart Poettering <lenn...@poettering.net> wrote: > On Sun, 22.11.15 15:26, Francis Moreau (francis.m...@gmail.com) wrote: > >> Hi, >> >> While rebooting, It seems to me that shutting down services while >> unmounting some

[systemd-devel] umounting FS happens to be at the same time as shutting down services

Hi, While rebooting, It seems to me that shutting down services while unmounting some FS at the same time in an unordered fashion is not a good idea since unmounting a FS can happen before a service using this FS is stopped. Is this expected ? Thanks. -- Francis

Re: [systemd-devel] Property 'MemoryLimit' is RO when using the D-Bus API

On Sun, Nov 8, 2015 at 9:38 PM, Lennart Poettering <lenn...@poettering.net> wrote: > On Fri, 06.11.15 18:38, Francis Moreau (francis.m...@gmail.com) wrote: > >> Hi, >> >> I'm trying to change the MemoryLimit property of one the service unit >> running on my

[systemd-devel] Property 'MemoryLimit' is RO when using the D-Bus API

Hi, I'm trying to change the MemoryLimit property of one the service unit running on my system by using 'busctl set-property ...' but getting the following error : Property 'MemoryLimit' is not writable. However using 'systemctl set-property' works as expected. I thought that 'systemctl

Re: [systemd-devel] Showing a more accurate version of systemd with the git sha1

On Fri, Oct 2, 2015 at 7:17 PM, Andrei Borzenkov <arvidj...@gmail.com> wrote: > 02.10.2015 19:27, Francis Moreau пишет: >> >> Hello, >> >> I'd like to know if it would be possible to show the git version (the >> one given by git-describe) when using the sy

[systemd-devel] Showing a more accurate version of systemd with the git sha1

Hello, I'd like to know if it would be possible to show the git version (the one given by git-describe) when using the systemd binaries with --version option. That would be specially usefull when the systemd tree used to build the binary was not a released one. I'm really not an automake stuff

Re: [systemd-devel] Implicit unit dependency on slice might be too weak ?

On Wed, Sep 30, 2015 at 11:06 PM, Lennart Poettering <lenn...@poettering.net> wrote: > On Tue, 22.09.15 15:52, Lennart Poettering (lenn...@poettering.net) wrote: > >> On Mon, 21.09.15 16:50, Francis Moreau (francis.m...@gmail.com) wrote: >> >> > Hi, >> >

Re: [systemd-devel] Implicit unit dependency on slice might be too weak ?

On 09/22/2015 03:52 PM, Lennart Poettering wrote: > On Mon, 21.09.15 16:50, Francis Moreau (francis.m...@gmail.com) wrote: > >> Hi, >> >> If a unit depends on a slice, a Wants=machine.slice is automatically >> added to the unit constraints. >> >> Wh

Re: [systemd-devel] Implicit unit dependency on slice might be too weak ?

Hello, On Mon, Sep 21, 2015 at 7:43 PM, David Herrmann <dh.herrm...@gmail.com> wrote: > Hi > > On Mon, Sep 21, 2015 at 4:50 PM, Francis Moreau <francis.m...@gmail.com> > wrote: >> Hi, >> >> If a unit depends on a slice, a Wants=machine.slice is auto

Re: [systemd-devel] systemd-firstboot skip root password initialisation if /etc/shadow is present

Hello, On Mon, Sep 21, 2015 at 7:45 PM, David Herrmann <dh.herrm...@gmail.com> wrote: > Hi > > On Fri, Sep 18, 2015 at 6:31 PM, Francis Moreau <francis.m...@gmail.com> > wrote: >> Hi, >> >> I find odd that systemd-firstboot skips root password in

Re: [systemd-devel] Implicit unit dependency on slice might be too weak ?

On Tue, Sep 22, 2015 at 2:18 PM, Zbigniew Jędrzejewski-Szmek <zbys...@in.waw.pl> wrote: > On Tue, Sep 22, 2015 at 11:52:05AM +0200, Francis Moreau wrote: >> On Tue, Sep 22, 2015 at 11:14 AM, David Herrmann <dh.herrm...@gmail.com> >> wrote: >> > Hi >&g

Re: [systemd-devel] systemd-firstboot skip root password initialisation if /etc/shadow is present

On Tue, Sep 22, 2015 at 11:16 AM, David Herrmann <dh.herrm...@gmail.com> wrote: > Hi > > On Tue, Sep 22, 2015 at 11:07 AM, Francis Moreau <francis.m...@gmail.com> > wrote: >> Hello, >> >> On Mon, Sep 21, 2015 at 7:45 PM, David Herrmann <dh.herrm...@gma

Re: [systemd-devel] Implicit unit dependency on slice might be too weak ?

On Tue, Sep 22, 2015 at 11:14 AM, David Herrmann <dh.herrm...@gmail.com> wrote: > Hi > > On Tue, Sep 22, 2015 at 10:58 AM, Francis Moreau <francis.m...@gmail.com> > wrote: [...] >>> >> >> But what if the slice fails to start ? >> >> Will t

Re: [systemd-devel] systemd-firstboot skip root password initialisation if /etc/shadow is present

On Tue, Sep 22, 2015 at 12:19 PM, David Herrmann <dh.herrm...@gmail.com> wrote: > On Tue, Sep 22, 2015 at 11:59 AM, Francis Moreau <francis.m...@gmail.com> > wrote: [...] >> >> Well during package installation done by the installer, some packages, >> us

Re: [systemd-devel] systemd-firstboot skip root password initialisation if /etc/shadow is present

On Tue, Sep 22, 2015 at 2:35 PM, David Herrmann <dh.herrm...@gmail.com> wrote: > Hi > > On Tue, Sep 22, 2015 at 2:26 PM, Francis Moreau <francis.m...@gmail.com> > wrote: >> On Tue, Sep 22, 2015 at 12:19 PM, David Herrmann <dh.herrm...@gmail.com> >> w

[systemd-devel] Implicit unit dependency on slice might be too weak ?

Hi, If a unit depends on a slice, a Wants=machine.slice is automatically added to the unit constraints. Why is "Requires=machine.slice" not prefered instead ? Thanks. -- Francis ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org

Re: [systemd-devel] Question related to cgroup and systemd

Hello Lennart, On Fri, Sep 18, 2015 at 2:24 PM, Lennart Poettering <lenn...@poettering.net> wrote: > B1;4002;0cOn Fri, 18.09.15 14:11, Francis Moreau (francis.m...@gmail.com) > wrote: > >> Hi, >> >> I'm trying to understand how cgroup is used by systemd and

[systemd-devel] Question related to cgroup and systemd

Hi, I'm trying to understand how cgroup is used by systemd and having the following behaviour that I don't understand. I've created a slice "myslice.slice" with this resource constraint "MemoryLimit=1024" and started it. I was expecting to find a trace of myslice in /sys/fs/cgroup/memory folder

[systemd-devel] systemd-firstboot skip root password initialisation if /etc/shadow is present

Hi, I find odd that systemd-firstboot skips root password init if /etc/shadow exists because AFAICS this file is always part of a minimal rootfs after being setup by an installer. Indeed it's populated during package installation. So I can't see a case where systemd-firstboot would prompt for a

Re: [systemd-devel] Possible confusion with socket activation and daemon own configuration

On 09/08/2015 07:48 PM, Simon McVittie wrote: > On 08/09/15 13:55, Francis Moreau wrote: >> On 09/08/2015 12:09 PM, Richard Maw wrote: >>> I understood that the common configuration for socket activated sshd was to >>> have a sshd.service for if you want it to al

Re: [systemd-devel] Possible confusion with socket activation and daemon own configuration

On 09/07/2015 11:28 AM, Richard Maw wrote: > On Sun, Sep 06, 2015 at 12:43:51PM +0200, Francis Moreau wrote: >> How is this handled ? Should we put a big warning in sshd_config to hint >> user to configure ListenAddress in sshd.socket in the case socket >> activation is used ?

Re: [systemd-devel] Possible confusion with socket activation and daemon own configuration

On 09/08/2015 12:09 PM, Richard Maw wrote: > On Tue, Sep 08, 2015 at 10:05:05AM +0200, Francis Moreau wrote: >> On 09/07/2015 11:28 AM, Richard Maw wrote: >>> On Sun, Sep 06, 2015 at 12:43:51PM +0200, Francis Moreau wrote: >>>> How is this handled ? Should we pu

Re: [systemd-devel] Delaying device service creation

On 07/03/2015 01:22 PM, Lennart Poettering wrote: B1;4002;0cOn Fri, 03.07.15 13:09, Francis Moreau (francis.m...@gmail.com) wrote: That's not an issue really. Since the device will not have any disk label initially, and thus nothing will make use of it, until the mke2fs is finished

Re: [systemd-devel] Delaying device service creation

On 07/03/2015 11:08 AM, Lennart Poettering wrote: On Tue, 30.06.15 17:37, Francis Moreau (francis.m...@gmail.com) wrote: Hi, I have a service 'A' which creates a device 'X' and does some configuring of the device. The device is created in a 'ExecStart=' directive whereas its configuration

Re: [systemd-devel] Delaying device service creation

On 07/03/2015 12:18 PM, Lennart Poettering wrote: On Fri, 03.07.15 11:53, Francis Moreau (francis.m...@gmail.com) wrote: On 07/03/2015 11:08 AM, Lennart Poettering wrote: On Tue, 30.06.15 17:37, Francis Moreau (francis.m...@gmail.com) wrote: Hi, I have a service 'A' which creates a device

Re: [systemd-devel] Delaying device service creation

On 06/30/2015 07:47 PM, Mantas Mikulėnas wrote: Options: - Configure it as part of ExecStart if possible. I don't see how is this going to help, sorry. - Configure it using a second .service unit (oneshot), and depend on that one. You meant all services that were depending on the device

[systemd-devel] Delaying device service creation

Hi, I have a service 'A' which creates a device 'X' and does some configuring of the device. The device is created in a 'ExecStart=' directive whereas its configuration happens during 'ExecStartPost='. But it seems that as soon as the device is seen by systemd, it creates the corresponding

Re: [systemd-devel] Question about ExecStartPost= and startup process

On 06/29/2015 10:05 AM, Andrei Borzenkov wrote: [...] service_sigchld_event() { ... } else if (s-control_pid == pid) { ... if (s-control_command s-control_command-command_next f ==

Re: [systemd-devel] Question about ExecStartPost= and startup process

On 06/28/2015 07:21 PM, Reindl Harald wrote: Am 28.06.2015 um 19:02 schrieb Francis Moreau: On 06/28/2015 01:01 PM, Reindl Harald wrote: Am 28.06.2015 um 12:00 schrieb Francis Moreau: Hello, For services with Type=Forking, I'm wondering if systemd proceeds starting follow-up units

Re: [systemd-devel] Question about ExecStartPost= and startup process

On 06/28/2015 07:35 PM, Andrei Borzenkov wrote: В Sun, 28 Jun 2015 19:02:57 +0200 Francis Moreau francis.m...@gmail.com пишет: On 06/28/2015 01:01 PM, Reindl Harald wrote: Am 28.06.2015 um 12:00 schrieb Francis Moreau: Hello, For services with Type=Forking, I'm wondering if systemd

[systemd-devel] Question about ExecStartPost= and startup process

Hello, For services with Type=Forking, I'm wondering if systemd proceeds starting follow-up units when the command described by ExecStart= exits or when the one described by ExecStartPost= exits ? I tried to read the source code to figure this out and it *seems* that the latter is true but I'm

Re: [systemd-devel] Question about ExecStartPost= and startup process

On 06/28/2015 01:01 PM, Reindl Harald wrote: Am 28.06.2015 um 12:00 schrieb Francis Moreau: Hello, For services with Type=Forking, I'm wondering if systemd proceeds starting follow-up units when the command described by ExecStart= exits or when the one described by ExecStartPost= exits

[systemd-devel] Failed to mount a crypted device with 'tmp' option

Hi, I'm setting up an encrypted device at boot using cryptsetup. This device is formatted at each boot (I'm using 'tmp' option in /etc/crypttab). Also this device is mounted at boot time (a corresponding entry in /etc/fstab has been made) and is also fsck'ed (fs_passno=2). However it seems that

Re: [systemd-devel] Help needed for optimizing my boot time

On 06/11/2015 06:23 PM, Dan Williams wrote: On Thu, 2015-06-11 at 15:15 +0200, Francis Moreau wrote: [...] Does ntpd service really need 'After=network.target', not sure. The 'network online' targets are really just there for ignorant services that don't respond to network events themselves

Re: [systemd-devel] Help needed for optimizing my boot time

On 06/12/2015 06:26 PM, Andrei Borzenkov wrote: В Fri, 12 Jun 2015 16:56:08 +0200 Francis Moreau francis.m...@gmail.com пишет: On 06/11/2015 06:23 PM, Dan Williams wrote: On Thu, 2015-06-11 at 15:15 +0200, Francis Moreau wrote: [...] Does ntpd service really need 'After=network.target

[systemd-devel] Help needed for optimizing my boot time

Hello, I'm interested in optimizing my boot time on my laptop. So I looked at the big picture first: $ systemd-analyze Startup finished in 3.994s (firmware) + 7.866s (loader) + 8.226s (kernel) + 7.921s (userspace) = 28.007s and noticed that the boot time spent in userspace is quite high.

Re: [systemd-devel] Help needed for optimizing my boot time

Hi, On 06/11/2015 12:44 PM, Andrei Borzenkov wrote: On Thu, Jun 11, 2015 at 1:08 PM, Francis Moreau francis.m...@gmail.com wrote: Hello, I'm interested in optimizing my boot time on my laptop. So I looked at the big picture first: $ systemd-analyze Startup finished in 3.994s

Re: [systemd-devel] Help needed for optimizing my boot time

On 06/11/2015 01:40 PM, Andrei Borzenkov wrote: On Thu, Jun 11, 2015 at 2:26 PM, Francis Moreau francis.m...@gmail.com wrote: $ systemd-analyze critical-chain graphical.target @7.921s multi-user.target @7.921s autofs.service @7.787s +132ms network-online.target

Re: [systemd-devel] Help needed for optimizing my boot time

On 06/11/2015 02:22 PM, Andrei Borzenkov wrote: On Thu, Jun 11, 2015 at 3:10 PM, Francis Moreau francis.m...@gmail.com wrote: On 06/11/2015 01:40 PM, Andrei Borzenkov wrote: On Thu, Jun 11, 2015 at 2:26 PM, Francis Moreau francis.m...@gmail.com wrote: $ systemd-analyze critical-chain

Re: [systemd-devel] Help needed for optimizing my boot time

On 06/11/2015 01:40 PM, Andrei Borzenkov wrote: On Thu, Jun 11, 2015 at 2:26 PM, Francis Moreau francis.m...@gmail.com wrote: $ systemd-analyze critical-chain graphical.target @7.921s multi-user.target @7.921s autofs.service @7.787s +132ms network-online.target

Re: [systemd-devel] multi-user.target only wants network.service if I'm doing 'systemct show runlevel3.target'

On 12/10/2014 10:19 AM, Francis Moreau wrote: Hello, On 12/10/2014 07:23 AM, Ivan Shapovalov wrote: On Tuesday 09 December 2014 at 17:25:48, Francis Moreau wrote: Hello Lennart, Thanks for answering ! On 12/09/2014 02:10 PM, Lennart Poettering wrote: On Tue, 09.12.14 11:19

Re: [systemd-devel] multi-user.target only wants network.service if I'm doing 'systemct show runlevel3.target'

Hello, On 12/10/2014 07:23 AM, Ivan Shapovalov wrote: On Tuesday 09 December 2014 at 17:25:48, Francis Moreau wrote: Hello Lennart, Thanks for answering ! On 12/09/2014 02:10 PM, Lennart Poettering wrote: On Tue, 09.12.14 11:19, Francis Moreau (francis.m...@gmail.com) wrote

[systemd-devel] multi-user.target only wants network.service if I'm doing 'systemct show runlevel3.target'

Hello, I've a very weird behaviour with systemd 217: # systemctl show -p Wants multi-user.target | grep network.service # systemctl show -p Wants runlevel3.target | grep network.service Wants= ... network.service ... # systemctl show -p Wants multi-user.target | grep network.service Wants=...

Re: [systemd-devel] multi-user.target only wants network.service if I'm doing 'systemct show runlevel3.target'

Hello Lennart, Thanks for answering ! On 12/09/2014 02:10 PM, Lennart Poettering wrote: On Tue, 09.12.14 11:19, Francis Moreau (francis.m...@gmail.com) wrote: Hello, I've a very weird behaviour with systemd 217: # systemctl show -p Wants multi-user.target | grep network.service

[systemd-devel] gummiboot can't be installed on ESP which is soft RAID1 metadata=0.9 partition

Hello, gummiboot install fails when ESP is MD RAID1 device using metadata 0.9 or 1.0. I don't think using such RAID for ESP would lead to issue. Is there any reason gummiboot doesn't want to be installed on such partition ? Thanks. ___ systemd-devel

Re: [systemd-devel] gummiboot can't be installed on ESP which is soft RAID1 metadata=0.9 partition

On 04/14/2014 06:16 PM, Lennart Poettering wrote: On Mon, 14.04.14 18:01, Francis Moreau (francis.m...@gmail.com) wrote: Hello, gummiboot install fails when ESP is MD RAID1 device using metadata 0.9 or 1.0. I don't think using such RAID for ESP would lead to issue. Is there any reason

Re: [systemd-devel] gummiboot can't be installed on ESP which is soft RAID1 metadata=0.9 partition

On 04/14/2014 06:38 PM, Kay Sievers wrote: On Mon, Apr 14, 2014 at 9:22 AM, Francis Moreau francis.m...@gmail.com wrote: On 04/14/2014 06:16 PM, Lennart Poettering wrote: On Mon, 14.04.14 18:01, Francis Moreau (francis.m...@gmail.com) wrote: gummiboot install fails when ESP is MD RAID1

Re: [systemd-devel] gummiboot can't be installed on ESP which is soft RAID1 metadata=0.9 partition

On 04/14/2014 08:11 PM, Thomas Bächler wrote: Am 14.04.2014 18:16, schrieb Lennart Poettering: On Mon, 14.04.14 18:01, Francis Moreau (francis.m...@gmail.com) wrote: Hello, gummiboot install fails when ESP is MD RAID1 device using metadata 0.9 or 1.0. I don't think using such RAID for ESP