write only in rsyncd.conf

2004-03-25 Thread Andrew Pimlott
A while back, there was a patch for a "write only" option in rsyncd.conf[1]. I use rsync for network backups, and I would be slightly more comfortable if other hosts couldn't read their backups (even though they can clobber them). Imagine that I scrub some sensitive data just before someone steal

--link-dest mostly useless on a server without chroot

2004-03-25 Thread Andrew Pimlott
When using the rsync server without chroot, the --link-dest and --compare-dest options are almost useless. This is because sanitize_paths is called on the link-dest directory, stripping out leading dots and slashes. Thus, the only possiblitiy for a link-dest directory is under the target director

exclude confusion: what does it match against?

2004-03-25 Thread Andrew Pimlott
The exact filename tested against include/exclude patterns is not always obvious, and the documentation is somewhat ambiguous about it. This bites particularly when using patterns starting with '/'. I just spent an hour being confused by this. Here are some suggested edits to the documentation.

Re: Fwd: RSync Progress Report Request

2004-03-25 Thread Jim Salter
I'd still prefer to see something like a --total-progress option that displayed the percentage of the total synchronization that had been completed, rather than the percentage of progress of the current file. In the occasions where I'm hovering impatiently over an rsync waiting for it to finish

Fwd: RSync Progress Report Request

2004-03-25 Thread Anthony Thyssen
I would line to see a -progress_time {sec} type option, which wil only show the progress of a file after that file has already taken more than {sec} to transfer. This could also ne a useful addition to the compond -P option, say with a argument of 5 seconds. Situation... I use RSync all the t

Re: Per-directory .cvsignore too aggressive

2004-03-25 Thread Wayne Davison
On Thu, Mar 25, 2004 at 10:26:24AM -0500, Szymon M. Rusinkiewicz wrote: > I have noticed that the contents of per-directory .cvsignore files apply > outside their subtrees when using --cvs-exclude in rsync 2.6.0. First off, thanks for the complete bug report -- it was very well done. However, the

Re: Root access over ssh?

2004-03-25 Thread Tim Conway
yes You have to have a "uid = 0" in the rsyncd.conf file for that module, since only root can give away files, and also bypass all (except over NFS, etc.) file protections. For (insert diety's name here)'s sake, don't use "/" for a path, and don't leave it un-chrooted, unless you're putting up

Re: Root access over ssh?

2004-03-25 Thread Jim Salter
There are any number of reasons you might still need or want rsync to run as root. For one, if you're rsyncing *to* the remote machine rather than *from* it, you might want to preserve access times, permissions, and ownerships - and you've got to be root on the remote system in order to do tha

Re: Root access over ssh?

2004-03-25 Thread Brian Chase
I'm not the command line guru, but it is my understanding that if you've got rsyncd running at boot time, any user can rsync over ssh to his or her home directories without requiring root access. I can't imagine a time when you'd need them to access other directories, except maybe /var/html and

Re: Root access over ssh?

2004-03-25 Thread Jim Salter
You can use the --rsh="/path/to/command/here" argument in conjunction with a simple shell script wrapper that calls rsync using sudo. Jim Salter JRS Systems Paul Galbraith wrote: Is it possible to configure rsync in server mode, to gain access to root protected files, without the user having to

Root access over ssh?

2004-03-25 Thread Paul Galbraith
Is it possible to configure rsync in server mode, to gain access to root protected files, without the user having to log in as root through ssh? I'd prefer to login as a regular user through ssh and access an rysnc server on the host that's running as root. As far as I can tell, however, that'

Per-directory .cvsignore too aggressive

2004-03-25 Thread Szymon M. Rusinkiewicz
I have noticed that the contents of per-directory .cvsignore files apply outside their subtrees when using --cvs-exclude in rsync 2.6.0. In the results below, notice how dir1/.cvsignore is applying to a file in dir2. There is no ~/.cvsignore, and the CVSIGNORE variable is unset. % ls -AFR .: dir1

Re: rsync 2.6.1pre-1 released

2004-03-25 Thread Paul Slootman
On Wed 24 Mar 2004, Wayne Davison wrote: > > Yes, I was justing thinking that I should bundle CVS up into a pre- > release and get some final testing before getting 2.6.1 out the door. > So, I just ran the packaging process that generated a release of > 2.6.1pre-1: > > http://rsync.samba.org/

Re: files deleted on server end during transfer (+my bug +patch suggestion)

2004-03-25 Thread Hans Eric Sandström
Ok, this is a late response but I was browsing thru the archives and found this question on a problem that I have been pondering myself. Answer: There is no problem if a file gets deleted during transfer since the file is kept open on the sending side and it will disappear only after the transfer