On Tue, Dec 23, 2003 at 04:59:20AM +0100, [EMAIL PROTECTED] wrote:
rsync -avv --delete --delete-excluded server::public/$i dest/
Look in the server's log file -- rsync puts some of the messages there
out of paranoia about exposing too much about the server's setup to the
end user. It may well
Hi,
I'm transfering a whole linux root dir (+ subdirs) to a backup location.
I tried -avr and -avrc switches.
My problem is that rsync somewhat seems to transfer nearly everything (2960
files!) while only maybe 10 or 15 were changed.
I'm backing up over gsm, so i got a high phone bill and very
On Tue, Dec 23, 2003 at 01:35:09AM -0800, Hannes Kocznar wrote:
Hi,
I'm transfering a whole linux root dir (+ subdirs) to a backup location.
I tried -avr and -avrc switches.
My problem is that rsync somewhat seems to transfer nearly everything (2960
files!) while only maybe 10 or 15 were
Look in the server's log file -- rsync puts
some of the messages there out of paranoia
about exposing too much about the server's
setup to the end user. It may well be that
rsync is being too paranoid in this instance.
..wayne..
Is there any way to *change* that behavior, particularly if
[EMAIL PROTECTED] wrote:
On Tue, Dec 23, 2003 at 04:00:24AM +0100, [EMAIL PROTECTED]
May the file-list is getting a bit to big for rsync?
If I splitt the transfer using
for i in *; do
rsync -avv --delete --delete-excluded server::public/$i dest/
done
it works seamlessly. The file list is
The rsync command tries to send sample_file to the backup server,
which cannot write it because it was not able to recurse into
my_directory.
Removing the -p switch and removing the backup file did not succeed,
and rsync continued to preserve the perms even without the switch. I am
running
Jim Salter wrote:
The rsync command tries to send sample_file to the backup server,
which cannot write it because it was not able to recurse into
my_directory.
Removing the -p switch and removing the backup file did not succeed,
and rsync continued to preserve the perms even without
yeah, except that the directory is not 700 but 600, so even user backup
cannot traverse it... but root can.
Ah, I see. Sounds like you're down to either running as root on both
ends, or ignoring errors.
Have you considered using sudo such that the fileserver isn't actually
logging into the
Ah, I see. Sounds like you're down to either running as root on both
ends, or ignoring errors.
Have you considered using sudo such that the fileserver isn't actually
logging into the backupserver as root, but only logging in as a
heavily *un*privileged account which can do nothing but run a
Or he could use SSH2 keys and an authorized_keys2 file,
Waxing pedantic, that really ought to be and/or. SSH2 keys are great as
an added layer of security to apply some paranoia as to *what* box is
calling the script, no matter what user account you're using to log in with.
allow root on
On Monday 22 Dec 2003 6:27 pm, Linda W wrote:
On Saturday 20 Dec 2003 13:18, Douglas Beethe wrote:
rsync -a xyz //somehost/abc # Source: WinXP, Target: Win2K
I noticed the snippet in the above post using the // notation.
Is that notation supposed to work?
(snip)
-linda
I use the
I have configured my rcyncd.conf file and it is stored in /etc.
Whne I type in the command rsync --daemon, nothing happens.
Whats wrong? I type in netstat to see if I can see port 873 being
used but there is nothing. Here is my conf file
log file = /var/log/rsyncd.log
[home]
path =
kevin_david_carpenter wrote:
I have configured my rcyncd.conf file and it is stored in /etc.
Whne I type in the command rsync --daemon, nothing happens.
Whats wrong? I type in netstat to see if I can see port 873 being
used but there is nothing. Here is my conf file
log file =
On Tue, Dec 23, 2003 at 10:25:04PM -, kevin_david_carpenter wrote:
When I type in the command rsync --daemon, nothing happens.
If you mean it returns to the command prompt without outputting
anything, that is what it does. You should see it running in the
output of the ps -ef command,
14 matches
Mail list logo
