summaryrefslogtreecommitdiff
path: root/systemd
diff options
context:
space:
mode:
authorScott Moser <smoser@ubuntu.com>2016-03-03 17:49:10 -0500
committerScott Moser <smoser@ubuntu.com>2016-03-03 17:49:10 -0500
commit77a9dbb4aa7e555d4c033c54a60b7084b2ab3373 (patch)
tree091464f87b6fb0225b92158dfb81742a72e70c1d /systemd
parentfa5c11836cec515dd23efcfabe9b736edd47c22a (diff)
downloadvyos-cloud-init-77a9dbb4aa7e555d4c033c54a60b7084b2ab3373.tar.gz
vyos-cloud-init-77a9dbb4aa7e555d4c033c54a60b7084b2ab3373.zip
cloud-init.target should not do anything
no wants or after or before.
Diffstat (limited to 'systemd')
-rw-r--r--systemd/cloud-init.target10
1 files changed, 0 insertions, 10 deletions
diff --git a/systemd/cloud-init.target b/systemd/cloud-init.target
index 03f61002..a63babb0 100644
--- a/systemd/cloud-init.target
+++ b/systemd/cloud-init.target
@@ -2,15 +2,5 @@
# To disable it you can either:
# a.) boot with kernel cmdline of 'cloudinit=disabled'
# b.) touch a file /etc/cloud/cloud-init.disabled
-# cloud-init normally emits a "cloud-config" upstart event to inform third
-# parties that cloud-config is available, which does us no good when we're
-# using systemd. cloud-config.target serves as this synchronization point
-# instead. Services that would "start on cloud-config" with upstart can
-# instead use "After=cloud-config.target" and "Wants=cloud-config.target"
-# as appropriate.
-
[Unit]
Description=Cloud-init target
-Wants=cloud-init-local.service cloud-init.service
-After=cloud-init-local.service cloud-init.service
-