--On Wednesday, January 07, 2004 03:10:23 -0800 jw schultz <[EMAIL PROTECTED]>
wrote:
I've lost track of the number of times someone has
complained on this list because blah/blah/* didn't behave as
he expected and the problem went away when he dropped the
unnecessary wildcard.
Hmmm... given the
On Wed, Jan 07, 2004 at 10:26:16AM -, Jon Hirst wrote:
> Having had a night to sleep on this I think rsync's limit
> on filename globbing needs pointing out more clearly.
>
> I think we need:
>
> 1) An entry in the FAQ (Done)
>
> 2) A better error message from rsync when it exceeds the
>
D]'
Subject: Re: Problem with many files in rsync server directory ?
On Tue, Jan 06, 2004 at 05:05:16PM -, Jon Hirst wrote:
> $ rsync [EMAIL PROTECTED]::gsh/* .
There's a limit to how many files you can glob with a wildcard. Just
remove the wildcard and let rsync transfer the
the files from
the directory.
Thanks very much for the quick answer.
Jon
-Original Message-
From: Wayne Davison [mailto:[EMAIL PROTECTED]
Sent: 06 January 2004 17:30
To: Jon Hirst
Cc: '[EMAIL PROTECTED]'
Subject: Re: Problem with many files in rsync server directory ?
On T
On Tue, Jan 06, 2004 at 05:05:16PM -, Jon Hirst wrote:
> $ rsync [EMAIL PROTECTED]::gsh/* .
There's a limit to how many files you can glob with a wildcard. Just
remove the wildcard and let rsync transfer the whole directory:
rsync [EMAIL PROTECTED]::gsh/ .
While you're at it, you should
Hi all,
I've been running rsync successfully from cron jobs for the last six months
across a local network. The cron jobs are very simple. They run rsync on a
client machine, connect to an rsync server on a server machine (no ssh or
rsh involved), and copy files from the server to the client. T
