code 12 error when specifying files

Erik Jacobs erik.jacobs at
Thu Aug 3 12:16:54 GMT 2006


That works brilliantly, but I think I'm still doing something wrong.

rsync --exclude="*" --include=".*" -Lputzogv user at node::folder /home/user/folder

client: nothing to do: perhaps you need to specify some filenames or the --recursive option?

I've also tried adding trailing slashes.

If I add the recursive option, it works, but I don't want to recurse -- I only want to look at the files in this folder... I guess I'm still a relative rsync newb... Specifying the wildcard (user at node::folder/.*) used to be the way to solve this problem... but I can't do that anymore because that's what's causing the problem in the first place...



-----Original Message-----
From: Matt McCutchen [mailto:hashproduct+rsync at]
Sent: Wednesday, August 02, 2006 5:54 PM
To: Erik Jacobs
Cc: rsync
Subject: Re: code 12 error when specifying files

On 8/2/06, Erik Jacobs <erik.jacobs at> wrote:
> We have a file structure on our servers which involves a folder that contains  hundreds of info files about particular things that all look like this format:  .a.b.c(.old/.new)
> But if I choose a wildcard which contains a  LOT of files:
> rsync user at node::filefolder/.7.*
> I get error in rsync protocol data stream (code 12)
> What I don't understand is why using the wildcard creates this  problem.

The problem in all of these cases is probably that the shell on your
local machine is expanding the wildcard.  If you add "echo" at the
beginning of the command line, you will see the exact arguments that
are being given to the rsync daemon.  Consider using filters instead
to select the files you want, like this:
        rsync --include=".7.*" --exclude="*" user at node::filefolder


More information about the rsync mailing list