FWIW, I ran without -x and still get the same error
--bill
Does it happen if you don't use '-x'? If both directories are on the
same filesystem, you shouldn't have any need for it.
I'm not sure what the specific problem is, but I do see that the
skip_filesystem() function calls
Does it happen if you don't use '-x'? If both directories are on the
same filesystem, you shouldn't have any need for it.
I'm not sure what the specific problem is, but I do see that the
skip_filesystem() function calls link_stat so perhaps somehow the
empty string is getting passed in there.
OK, but I'm not exactly sure what I'm looking for...
I don't think the link error is caused by my data (I have no symlinks).
For whatever reason, it appears that a blank is leading the file list,
and the 'stat' on NULL is what is causing the link_stat error.
write(1, b u i l d i n g f i
I suggest running truss -f -o trussfile before that command and look for
the error in the trussfile and see what's happening just before it. Under
some circumstances rsync can print that message when a symlink goes
nowhere, but I'm not sure what the circumstances are. Perhaps it does that
What is the command you are running?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On
Behalf Of Bill Houle
Sent: Monday, 1 January 1601 11:00 AM
To: [EMAIL PROTECTED]
Subject: I/O error when deleting files
When I run rsync in no-op mode, all appears
