From b5c3659c29db2177665ff6c1c10587bc1d8eba1f Mon Sep 17 00:00:00 2001 From: Scott Moser Date: Thu, 8 Jul 2010 20:52:54 -0400 Subject: add 'nobootwait' to the default options for fstab entries It just seems like for cloud instances, getting /etc/fstab written incorrectly with the result of non-booting system is worth avoiding. --- doc/examples/cloud-config.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'doc/examples/cloud-config.txt') diff --git a/doc/examples/cloud-config.txt b/doc/examples/cloud-config.txt index e036feba..ed1ef47f 100644 --- a/doc/examples/cloud-config.txt +++ b/doc/examples/cloud-config.txt @@ -102,7 +102,7 @@ packages: # written to /etc/fstab. # - '/dev' can be ommitted for device names that begin with: xvd, sd, hd, vd # - if an entry does not have all 6 fields, they will be filled in -# from the following: [ None, None, "auto", "defaults", "0", "0" ] +# from the following: [ None, None, "auto", "defaults,nobootwait", "0", "0" ] # # Note, that you should set 'nobootwait' (see man fstab) for volumes that may # not be attached at instance boot (or reboot) -- cgit v1.2.3