How to track down the lifespan of the device unit file, i.e. the activating state? I have an embedded system where systemd-analyze plot shows that the unit file I am interested in, let’s say dev-mmcpartition.device, takes about 2 seconds to be become active. This partition (mmcpartition) holds my rootfs. I would like to know what is going on during those 2 seconds, what device unit file is doing, how to track what it is doing? Thanks in advance. Best regards Elbek
device unit files
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: device unit files
- From: Elbek Mamajonov <emm.boxinuse@xxxxxxxxx>
- Date: Mon, 11 Apr 2022 23:16:28 +0900
- Follow-Ups:
- Re: device unit files
- From: Mantas Mikulėnas
- Re: device unit files
- Prev by Date: Re: trivial net connection logs - ?
- Next by Date: Trying to Understand "journalctl --verify" and trigger some errors
- Previous by thread: trivial net connection logs - ?
- Next by thread: Re: device unit files
- Index(es):
 |