diff options
| author | Richard Maw <richard.maw@codethink.co.uk> | 2013-06-09 22:56:33 +0000 |
|---|---|---|
| committer | Richard Maw <richard.maw@codethink.co.uk> | 2013-06-09 23:02:58 +0000 |
| commit | 3e8721c40abdc474ad3431d62d102e10aee7488f (patch) | |
| tree | 7788b3c34e3289acbb49daa3be44d4ffb8aed57a /nfsboot.write | |
| parent | 0b1db252d61c3aa02ae7c865314ee07e96244be3 (diff) | |
| download | definitions-3e8721c40abdc474ad3431d62d102e10aee7488f.tar.gz | |
Write extensions: pass -s to rsync
-s, or --protect-args prevents the file path components of destination
or source paths being interpreted by the remote shell.
This is for wildcards or other shell features, but it breaks when paths
have whitespace.
We tend to always use absolute paths, so all uses of rsync now pass -s.
kvm.write needs it, since the disk can be written to a path with spaces.
Nfsboot and ssh-rsync need it because version labels are used, which may
have spaces, and temporary directories are used, which could have spaces
in weird TMPDIR configurations.
Diffstat (limited to 'nfsboot.write')
| -rwxr-xr-x | nfsboot.write | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/nfsboot.write b/nfsboot.write index f43d3c98..34a72972 100755 --- a/nfsboot.write +++ b/nfsboot.write @@ -118,7 +118,7 @@ class NFSBootWriteExtension(morphlib.writeexts.WriteExtension): rsync_dest = 'root@%s:%s' % (location, kernel_dest) self.status(msg='Copying kernel') cliapp.runcmd( - ['rsync', kernel_src, rsync_dest]) + ['rsync', '-s', kernel_src, rsync_dest]) # Link the kernel to the right place self.status(msg='Creating links to kernel in tftp directory') @@ -153,7 +153,7 @@ class NFSBootWriteExtension(morphlib.writeexts.WriteExtension): self.status(msg='Creating \'orig\' rootfs') cliapp.runcmd( - ['rsync', '-aXSPH', '--delete', rootfs_src, + ['rsync', '-asXSPH', '--delete', rootfs_src, 'root@%s:%s' % (location, orig_path)]) self.status(msg='Creating \'run\' rootfs') |