Timeline for answer to systemd unit on separate partition fails to load on reboot by filbranden
Current License: CC BY-SA 4.0
Post Revisions
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 5, 2023 at 16:37 | comment | added | hariseldon78 | A clear error message would be enough... | |
| Jan 28, 2023 at 21:05 | comment | added | Pawel Veselov | I ran into something like this with 219. Systemd would not enable the service if link is to another partition with "Invalid argument" error, without ever explaining what exactly is wrong (yet agree to start/stop it). | |
| Mar 14, 2020 at 1:07 | comment | added | filbranden | @cdleonard Part of the problem is that you need a full picture to properly resolve dependencies. For example, what if the unit from the other partition declares it wants to run before starting a webserver or a database, but by the time it's available those services are already up? Also, recalculating the whole dependency graph is pretty expensive, so doing so when partitions being mounted means your boot will be slower. And systemd is all about fast boot. | |
| Mar 14, 2020 at 1:01 | comment | added | cdleonard | This is disappointing: systemd could just reload symlinks as partitions go up. | |
| Mar 14, 2020 at 1:01 | vote | accept | cdleonard | ||
| Mar 13, 2020 at 2:10 | history | answered | filbranden | CC BY-SA 4.0 |