From 77a9dbb4aa7e555d4c033c54a60b7084b2ab3373 Mon Sep 17 00:00:00 2001 From: Scott Moser Date: Thu, 3 Mar 2016 17:49:10 -0500 Subject: cloud-init.target should not do anything no wants or after or before. --- systemd/cloud-init.target | 10 ---------- 1 file changed, 10 deletions(-) (limited to 'systemd') 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 - -- cgit v1.2.3