On Sat, 20 Jun 2015, Dale Snell wrote:
> Argh... I meant the _source_ directory. (*sigh* not enough coffee.) The
> remote host's path has to be absolute, or rsync won't know where subdir
> and its files are.
Dale,
And that's what I provided (c.f. original post): 'rsync -avz
srchost:/directo
On Sat, 20 Jun 2015 07:11:48 -0700 (PDT), in message
alpine.LNX.2.11.1506200708210.8143@localhost, Rich Shepard wrote:
> On Sat, 20 Jun 2015, Dale Snell wrote:
>
> > If memory and my interpretation of the man page are correct (and
> > neither may be, I've not had my morning caffeine yet), rsync
>
On Sat, 20 Jun 2015, Dale Snell wrote:
> If memory and my interpretation of the man page are correct (and neither
> may be, I've not had my morning caffeine yet), rsync requires you to
> specify an absolute path for the destination. Hence
>
> rsync -avz host:/path/to/dir/subdir/ .
>
> should work
On Sat, 20 Jun 2015 05:44:24 -0700 (PDT), in message
alpine.LNX.2.11.1506200539350.8143@localhost, Rich Shepard wrote:
>A question for you professional admins: what situation might
> result in the command, 'rsync -avz host:directory/subdirctory/ .'
> reporting that the directory/subdirectory d
A question for you professional admins: what situation might result in the
command, 'rsync -avz host:directory/subdirctory/ .' reporting that the
directory/subdirectory does not exist on that host while the command, 'scp
host:directory/subdirctory/* .' work like a charm?
If I neglected to sp
