From a5d122c0b3a691dc26708b4d6657b74ba046e43a Mon Sep 17 00:00:00 2001 From: Girish Ramakrishnan Date: Mon, 7 Sep 2015 22:37:20 -0700 Subject: [PATCH] Leave a note on singleshot After= behavior "Actually oneshot is also a bit special and that is where RemainAfterExit comes in. For oneshot, systemd waits for the process to exit before it starts any follow-up units (and with multiple ExecStarts I assume it waits for all of them). So that automatically leads to the scheme in berbae's last post. However, with RemainAfterExit, the unit remains active even though the process has exited, so this makes it look more like "normal" service with " --- images/initializeBaseUbuntuImage.sh | 1 + 1 file changed, 1 insertion(+) diff --git a/images/initializeBaseUbuntuImage.sh b/images/initializeBaseUbuntuImage.sh index 111e9d8ea..a993b1524 100755 --- a/images/initializeBaseUbuntuImage.sh +++ b/images/initializeBaseUbuntuImage.sh @@ -200,6 +200,7 @@ EOF systemctl enable iptables-restore # Allocate swap files +# https://bbs.archlinux.org/viewtopic.php?id=194792 ensures this runs after do-resize.service echo "==== Install box-setup systemd script ====" cat > /etc/systemd/system/box-setup.service <