Just a correction to my example here:
On Tue, Jul 28, 2009 at 07:25:48AM -0700, Daniel Burrows
was heard to say:
> $ mkdir foo
> $ echo > --test
> $ rsync --test foo
> rsync error: syntax or usage error (code 1) at main.cc(1440)
> [client=3.0.6]
> $ rsync -- test foo
Ob
On Tue, 28 Jul 2009, Ron Johnson wrote:
Two points:
1. Always do it the "right way", even though you *assume* you
know the wrong way "should" work, and
2. parsers treat extraneous spaces in all sorts of nasty and
unexpected ways.
I'm finding that out. I guarantee the lesson will be reta
On Tue, Jul 28, 2009 at 12:40:00AM -0700, Robert Holtzman was
heard to say:
> On Mon, 27 Jul 2009, Mike Bird wrote:
>
> >On Mon July 27 2009 22:59:38 Robert Holtzman wrote:
> >>
> >>Just installed rsync 3.0.3-2 and tried to backup to a usb drive using a
> >>script:
> >>
> >>rsync -vaHz --exclude
On Tue, 28 Jul 2009, Sven Joachim wrote:
On 2009-07-28 09:35 +0200, Robert Holtzman wrote:
On Tue, 28 Jul 2009, Ron Johnson wrote:
rsync -vaHz --exclude '/proc' --exclude '/sys' -- exclude '*.iso'
Look *very* *carefully* at this line.
--exclude '/media' / /media/disk/laptop
and see ho
On 2009-07-28 02:40, Robert Holtzman wrote:
On Mon, 27 Jul 2009, Mike Bird wrote:
On Mon July 27 2009 22:59:38 Robert Holtzman wrote:
Just installed rsync 3.0.3-2 and tried to backup to a usb drive using a
script:
rsync -vaHz --exclude '/proc' --exclude '/sys' -- exclude '*.iso'
--exclude '/
On 2009-07-28 09:35 +0200, Robert Holtzman wrote:
> On Tue, 28 Jul 2009, Ron Johnson wrote:
>
>> On 2009-07-28 00:59, Robert Holtzman wrote:
>>> Just installed rsync 3.0.3-2 and tried to backup to a usb drive
>>> using a script:
>>>
>>> rsync -vaHz --exclude '/proc' --exclude '/sys' -- exclude '*.
On Mon, 27 Jul 2009, Mike Bird wrote:
On Mon July 27 2009 22:59:38 Robert Holtzman wrote:
Just installed rsync 3.0.3-2 and tried to backup to a usb drive using a
script:
rsync -vaHz --exclude '/proc' --exclude '/sys' -- exclude '*.iso'
--exclude '/media' / /media/disk/laptop
Does the space
On Tue, 28 Jul 2009, Ron Johnson wrote:
On 2009-07-28 00:59, Robert Holtzman wrote:
Just installed rsync 3.0.3-2 and tried to backup to a usb drive using a
script:
rsync -vaHz --exclude '/proc' --exclude '/sys' -- exclude '*.iso'
Look *very* *carefully* at this line.
--exclude '/media' /
On Mon July 27 2009 22:59:38 Robert Holtzman wrote:
> Tried to post this to the rsync list but the subscribe connection failed
> so I'll try here.
>
> Just installed rsync 3.0.3-2 and tried to backup to a usb drive using a
> script:
>
> rsync -vaHz --exclude '/proc' --exclude '/sys' -- exclude '*.i
On 2009-07-28 00:59, Robert Holtzman wrote:
Tried to post this to the rsync list but the subscribe connection failed
so I'll try here.
Just installed rsync 3.0.3-2 and tried to backup to a usb drive using a
script:
rsync -vaHz --exclude '/proc' --exclude '/sys' -- exclude '*.iso'
Look *ve
Tried to post this to the rsync list but the subscribe connection failed
so I'll try here.
Just installed rsync 3.0.3-2 and tried to backup to a usb drive using a
script:
rsync -vaHz --exclude '/proc' --exclude '/sys' -- exclude '*.iso'
--exclude '/media' / /media/disk/laptop
This is the
On Mon, Sep 12, 2005 at 11:31:47PM -0600, Bob Proulx wrote:
> Ric Otte wrote:
> > One thing I notice is that while copying the files (using either cp or
> > rsync (and also tar, although I didn't pay as much attention), is that
> > according to top, Xfree86 is often using up to 78-99% of the cpu, a
Ric Otte wrote:
> One thing I notice is that while copying the files (using either cp or
> rsync (and also tar, although I didn't pay as much attention), is that
> according to top, Xfree86 is often using up to 78-99% of the cpu, and
> things are very sluggish for a few seconds after the copying is
On Mon, Sep 12, 2005 at 04:13:24PM -0500, Ron Johnson wrote:
> What if you pipe stdout to a text file?
>
Ron,
I reformatted the drive, and began rsync with the errors piped to a
file (rsync -av --exclude-from=.rsync.all /home/ric /bkup/
2>xxx.rsync)
Things went fine for a long time, but eventually
On Mon, 2005-09-12 at 08:49 -0700, Ric Otte wrote:
> On Mon, Sep 12, 2005 at 03:07:41AM -0500, Ron Johnson wrote:
> > Does tar succeed as well?
> >
> Yes, I believe so. I just copied several directories using tar, and
> fsck says everything is fine.
>
> One thing I notice is that while copying t
On Mon, Sep 12, 2005 at 03:07:41AM -0500, Ron Johnson wrote:
> Does tar succeed as well?
>
Yes, I believe so. I just copied several directories using tar, and
fsck says everything is fine.
One thing I notice is that while copying the files (using either cp or
rsync (and also tar, although I didn
On Sun, 2005-09-11 at 21:53 -0700, [EMAIL PROTECTED] wrote:
> I have a SATA hard disk in my machine, and recently installed a 200gb Seagate
> IDE hard drive in it to use as backup. I want to use rsync to backup my home
> directory to this machine. I used mkfs.ext3 to format the drive as ext3, and
I have a SATA hard disk in my machine, and recently installed a 200gb Seagate
IDE hard drive in it to use as backup. I want to use rsync to backup my home
directory to this machine. I used mkfs.ext3 to format the drive as ext3, and
mounted the drive (mount -text3 /dev/hdc /bkup). I then made a d
While attempting to rsync a backup I get the below error on sarge after
it's run for awhile.. I guess eventually I could get it all copied.
:( Notice when I try to umount afterwards, the device is busy.
I'm using reiserfs on both drives.
*
sync: writefd_unbuffered failed t
On Thu, 04 Sep 2003 12:55:50 +0200
francois mounier <[EMAIL PROTECTED]> wrote:
> but when I run
> rsync 192.168.1.2::test/ /var/www
>
> it returns this error
> @ERROR: invalid gid nobody
> rsync: connection inexpectedly closed (39 bytes read so far)
> rsync error: error in rsync protocol data str
---
> francois mounier wrote:
>
> >it returns this error
> >@ERROR: invalid gid nobody
> >rsync: connection inexpectedly closed (39 bytes read so far)
> >rsync error: error in rsync protocol data stream (code 12) at
> >io.c(150)
> >
> I don't know if Debian is different, but rsync
francois mounier wrote:
it returns this error
@ERROR: invalid gid nobody
rsync: connection inexpectedly closed (39 bytes read so far)
rsync error: error in rsync protocol data stream (code 12) at
io.c(150)
I don't know if Debian is different, but rsync can work with its own
users and passwords (i
Hi
I am using Debian woody 3.0_r1 on hppa and rsync 2.5.6
I have several web servers and I d like to use rsync to keep my web
content up-to-date on each server. One of the server runs rsync as a
daemon the other are rsync clients...
So on all I have installed rsync package on all
>From my clien
> I have a problem using rsync which seems to give an error when copying files.
> Although it appears consistent for a given file, it is not consistent between
> files.
>
> If I issue this command
>
> rsync rabbit.home::alan/My\ Documents/Mail/Agent\ News\ Data/GROUPS.IDX .
>
> Some files for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I have a problem using rsync which seems to give an error when copying files.
Although it appears consistent for a given file, it is not consistent between
files.
If I issue this command
rsync rabbit.home::alan/My\ Documents/Mail/Agent\ News\ Dat
Hallo !
Ich habe mir die Pseudo-image-Dateien
heruntergeladen und möchte nun den rsync - Befehl ausführen. Jedoch gebe ich
nicht den richtigen CD-Image rsync - Server an. Ich kann auch nicht das
debian-CD - Verzeichnis auf irgend welchen mirror-Seiten finden. Ich bitte
um Hilfe.
Danke
Hi!
I've got a problem with rsync. my wish:
i want to get all binary-i386 packages of the potato distribution from
ftp.de.debian.org.
so i set up an includes file as follows:
- **/
- **/*
+ dists/potato/
+ dists/potato/*
+ dists/potato/*/
+ dists/potato/*/*
+ dists/potato/*/binary-i386/
+ dists/pot
27 matches
Mail list logo
