>>> Reindl Harald <h.reindl@xxxxxxxxxxxxx> schrieb am 13.01.2020 um 11:50 in Nachricht <efdc18c8-7396-02fc-1780-9e089e203601@xxxxxxxxxxxxx>: > > Am 13.01.20 um 11:45 schrieb Ulrich Windl: >>>>> Lennart Poettering <lennart@xxxxxxxxxxxxxx> schrieb am 07.01.2020 um 14:27 >>> Such a concept does not exist. I mean your service is a system >>> service itself, so what is that even supposed to mean that the service >>> shall start 5s after it already started? But even if you mean to say >>> "5s after all other services", then think how that falls apart if you >>> have multiple services declaring that. >> >> Maybe explain when systemd considers a service as started, pointing out > wrong >> implementations. > > https://www.freedesktop.org/software/systemd/man/systemd.service.html > > CTRL+F Type= > > for network it strongly depends on *how* your network is setup > (NetworkManager, systemd‑networkd, legacy /etc/nint.d/network or even a > own implementation) > > with the implementation below you can relieable oder anything after > "network‑up.service" or "network‑online.target" But isn't it simply because none of the ExecStarts is executing in background? The interesting part is DHCP which can complete quickly or not at all (e.g. configuration error)... ... > ExecStart=/usr/sbin/iptables‑legacy‑restore ‑w 5 /etc/sysconfig/iptables ... > ExecStart=‑/usr/sbin/sysctl ‑q ‑‑load=/etc/sysctl‑conntrack.conf ... > ExecStart=‑/usr/sbin/ethtool ‑G eth0 rx‑mini 0 ... > ExecStart=/usr/sbin/ip addr add 10.0.0.102/255.255.255.0 broadcast 10.0.0.255 dev eth0 ... > ExecStart=/usr/sbin/ip link set dev eth0 multicast off up ... > ExecStart=/usr/sbin/ip route add default via 10.0.0.1 ... > ExecStart=‑/usr/sbin/sysctl ‑e ‑p ‑q ... Regards, Ulrich _______________________________________________ systemd-devel mailing list systemd-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/systemd-devel