mirror of
https://git.proxmox.com/git/pve-installer
synced 2025-08-24 15:33:39 +00:00
0b961bc063
First of, multi-user.target does not seem to really provide any (strong) ordering guarantee, it seems. Instead, let the "fully-up" ordering from the auto-installer depend on the product-specific API proxy instead. That way, it is ensured that 1) the system really is fully up and 2) that users could even use the API / CLI commands, or write files to pmxcfs (in case of PVE). After= and Wants= ignore non-existent units, so we can just specify all three API proxy units here w/o any conditional. Suggested-by: Shannon Sterz <s.sterz@proxmox.com> Signed-off-by: Christoph Heiss <c.heiss@proxmox.com>
17 lines
594 B
Desktop File
17 lines
594 B
Desktop File
[Unit]
|
|
Description=Proxmox First Boot Setup (Fully Booted)
|
|
After=systemd-remount-fs.service pveproxy.service pmgproxy.service proxmox-backup-proxy.service
|
|
Wants=pveproxy.service pmgproxy.service proxmox-backup-proxy.service
|
|
ConditionPathExists=/var/lib/proxmox-first-boot/pending-first-boot-setup
|
|
ConditionPathIsReadWrite=/var/lib
|
|
|
|
[Service]
|
|
Type=oneshot
|
|
RemainAfterExit=yes
|
|
ExecStart=/var/lib/proxmox-first-boot/proxmox-first-boot fully-up
|
|
ExecStartPost=/usr/bin/rm -v /var/lib/proxmox-first-boot/pending-first-boot-setup
|
|
|
|
[Install]
|
|
Alias=proxmox-first-boot.service
|
|
WantedBy=multi-user.target
|