CLUE:Fairly mysterious rsync problem.
richard at rushlogistics.com
Mon Mar 14 13:23:05 GMT 2005
I added "max verbosity = 3" to rsyncd.conf. and tried
 rsync to test-data from ussbriscoe
 server_recv(1) starting pid=2628
 received 1 names
 recv_file_list done
 generator starting pid=2628 count=1
 delta transmission enabled
 recv_generator:failed to open "/test_briscoe"
(in test-data): Permission denied
 generate_files phase=1
 recv_files(1) starting
 recv_files phase 1
 generate_files phase=2
 generate_files finished
 recv_files finished
 wrote 28 bytes read 106 total size 14
 _exit_cleanup(code=0, file=mail.c, line=548):
about to call exit(0)
I did a chmod 777 test_briscoe (on the client) and
still got the same result.
If anyone can help. I would appreciate it.
--- Wayne Davison <wayned at samba.org> wrote:
> On Sun, Mar 13, 2005 at 07:41:36AM -0800, Richard
> Reina wrote:
> > rsync -vvv --stats --progress file1
> > 192.168.0.14::test-data
> > [...]
> > make_file(3,TEST2)
> This indicates that the file that was transferred
> was "TEST2", not
> "file1". Was that output from a different run? Or
> do you have
> something that is tweaking your command-line behind
> the scenes?
> > Number of files: 1
> > Number of files transferred: 0
> > Total file size: 9 bytes
> This tells you there was one file, 9 bytes long, but
> it was not
> transferred, presumably because it was up-to-date.
> The debug output for
> such decisions occurs on the daemon when it is the
> receiver, so you'll
> need to use a modern rsync on the daemon (e.g.
> 2.6.3) and specify
> "max verbosity = 3" in the rsyncd.conf file, at
> which point you will
> see a better description of what is happening in the
> server's log file
> (if you run the client command with -vvv again).
More information about the rsync