See https://github.com/coreos/ignition-dracut/pull/140 Basically, we do a lot of nontrivial stuff in the initramfs (Ignition) and this was re-starting some of our units, which I found surprising. The behavior seems to have come from https://github.com/systemd/systemd/commit/7d89ce303fb59743a4392eeb3110c00f100172ca Now, I understand the goal of having systemd re-load its configuration, but why do we need to start the initrd-fs.target unit again? Can't we assume that the mount points set up for the root are still active? _______________________________________________ systemd-devel mailing list systemd-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Why does initrd-parse-etc.service re-start initrd-fs.target?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: Why does initrd-parse-etc.service re-start initrd-fs.target?
- From: "Colin Walters" <walters@xxxxxxxxxx>
- Date: Thu, 05 Dec 2019 09:31:10 -0500
- Cc: harald@xxxxxxxxxx
- User-agent: Cyrus-JMAP/3.1.7-612-g13027cc-fmstable-20191203v1
- Follow-Ups:
- Re: Why does initrd-parse-etc.service re-start initrd-fs.target?
- From: Andrei Borzenkov
- Re: Why does initrd-parse-etc.service re-start initrd-fs.target?
- Prev by Date: Re: Thoughts about storing unit/job statistics
- Next by Date: VPN connections subject to hijack attack
- Previous by thread: Unexplainable delays in execution of parted and sfdisk
- Next by thread: Re: Why does initrd-parse-etc.service re-start initrd-fs.target?
- Index(es):
 |