"I haven't noticed this behavior myself, and attempted a repro here on
v253 (Arch x86_64) just now."
-> Sorry for being unclear, I am talking about an embedded system with very
significant customization (yocto based) and fully expect that the
customization introduced the issue, so I didn't expect
On Di, 12.12.23 19:06, Etienne Cordonnier (ecordonn...@snap.com) wrote:
> Hello,
> I am debugging some embedded system running systemd. The behavior I am
> observing is that many systemd targets such as multi-user.target are
> disabled after I run systemctl daemon-reload (as shown by systemctl
>
On Tue, Dec 12, 2023 at 07:06:22PM +0100, Etienne Cordonnier wrote:
> Hello,
> I am debugging some embedded system running systemd. The behavior I am
> observing is that many systemd targets such as multi-user.target are
> disabled after I run systemctl daemon-reload (as shown by systemctl
>
More specifically, basic.target, local-fs.target and multi-user.target are
disabled after I run systemctl daemon-reload.
On Tue, Dec 12, 2023 at 7:06 PM Etienne Cordonnier
wrote:
> Hello,
> I am debugging some embedded system running systemd. The behavior I am
> observing is that many systemd
Hello,
I am debugging some embedded system running systemd. The behavior I am
observing is that many systemd targets such as multi-user.target are
disabled after I run systemctl daemon-reload (as shown by systemctl
list-units --type target --all). This causes many systemd units to be
disabled, and
