On Fri, 22 Mar 2024, Tomas Kuchta wrote:
Errors with rsync usually mean that the file system changed - such as logs,
proc, sys, var, etc.
Tomas,
I thought this might be the cause. While I did nothing in the partitions
being sync'd the kernel or some other application might have made a change.
On Thu, Mar 21, 2024, 13:20 MC_Sequoia wrote:
> "I worry that the copy omitted content. Especially when the size reported
> as copied doesn't match the size of something like "du -s""
>
> rsync = remote synchronization of local & remote files. If there's no
> delta, there's no need to sync the fi
"I worry that the copy omitted content. Especially when the size reported as
copied doesn't match the size of something like "du -s""
rsync = remote synchronization of local & remote files. If there's no delta,
there's no need to sync the files.
On Thu, 21 Mar 2024, Michael Ewan wrote:
As others have said, capture the output, but instead of a pipe use
'--log-file=rsync.log' option. Also, when you run rsync the second time it
should only log the errors since all the files have been copied already.
Michael,
Good point. Will do so.
Th
On Thu, 21 Mar 2024, King Beowulf wrote:
you can tee stdout to a file
Ed,
True that. Didn't occur to me as I was focused on getting that replacement
drive set up.
$ rsync blah-blah 2>&1| | tee rsync.log
I'll do this the next new disk update.
Thanks,
Rich
"you can tee stdout to a file
>
> $ rsync blah-blah |2>&1| | tee rsync.log
"|2>&1" grabs both stdout and stderr. Now you can view rsyn.log at your
leisure."
Additionally, you can use -vv to increase verbosity and use -q so that only
errors get written out to a log file. Also, using the -n optio
On 3/20/24 17:19, Rich Shepard wrote:
> On Wed, 20 Mar 2024, wes wrote:
>
>> why wait a few days? you could run rsync again immediately and you can
>> look for errors.
> wes,
>
> Two reasons:
>
> 1) I'm waiting for the weekend to replace the desktop's internal hard drive.
> I'll run rsync the
On Wed, 20 Mar 2024, wes wrote:
why wait a few days? you could run rsync again immediately and you can
look for errors.
wes,
Two reasons:
1) I'm waiting for the weekend to replace the desktop's internal hard drive.
I'll run rsync then to update what changed from today.
2) The list o
After running for about an hour rsync ended this way:
-
sent 181,880,754,804 bytes received 1,336,778 bytes 43,642,973.39 bytes/sec
total size is 181,831,399,934 speedup is 1.00
rsync error: some files/attrs were not transferred (see previous errors) (code
23) at main.c(1327) [sender=3.2.5
On Wed, 20 Mar 2024, Michael Ewan wrote:
That should work.
Thanks, Michael.
Another linux lesson learned.
Regards,
Rich
My experience with rsync has been between hosts on the LAN and backups from
a desktop to the MediaSonic Probox external drive. My web searches for the
appropriate syntax between two drives on the same host finds nothing
suitable.
If I mount the new drive on /media/hd0 I wonder if this syntax will
For recursive mirroring common use would be
rsync -a --delete --progress sourceDir destinationDir/
Your example: rsync -a --delete /media/jjj/Movies /media/jjj/Synology/
Good way to see if you want to use --delete might be to count the number of
files to be updated and/or deleted with dry run '-
On Tue, 12 Jul 2016 17:10:39 -0700
John Jason Jordan dijo:
>And that brings up my immediate problem. Bear in mind that I want the
>destination to be a mirror of the source, hence my need for the
>--delete option. Unfortunately, it doesn't seem to be working. Here is
>my current command:
>
>
On Tue, 12 Jul 2016, John Jason Jordan wrote:
> I intend to make a script to run at 2am daily. To guard against losing
> the backup the script will first make sure that both source and
> destination are mounted. I haven't figured out yet how to do that, but
> it's in my plans. In the meantime I'm
On Fri, 08 Jul 2016 23:55:16 -0700
Tomas Kuchta dijo:
>if you add rsync --delete option then rsync will delete remote files
>as you describe. For the safety of your files, maybe you should
>consider enabling snapshots or do some safeguarding with your mirror
>scripts.
>
>It would be unfortunate t
You cannot change ownership of mounted filesystems. That must be done from
the remote end. Only the contents can be modified when you have
permissions.
You will probably need to figure out what the expected options are on the
NFS mount command. We mount our NAS at work as remote home directories
On Mon, 11 Jul 2016 19:05:46 -0700
Don Buchholz dijo:
>
>I think you're really close ...
>
>(1)
> sudo mount -t nfs
> 192.168.0.101:*/*volume1/Synology /media/jjj/Synology
>
>... that little "/" in front of 'volume1' could be important.
You may be onto something here. First, I thought th
I forgot to add - you must run (as root):
mount nfsClientMountDir
- if you want to mount the NFS share without reboot.
T
On Monday, July 11, 2016 07:17:18 PM you wrote:
> Here is simple example of NFS NAS and client (PC) configuration:
>
> Names and abreviations:
> * data - NFS server dir t
Here is simple example of NFS NAS and client (PC) configuration:
Names and abreviations:
* data - NFS server dir to be exported
* nfsServerIp - IP of NFS Server
* nfsClientIp - IP of NFS client (example: 192.168.1.100)
* networkIp - IP of your network (example: 192.168.1.1)
* nfsClientMo
I think you're really close ...
(1)
sudo mount -t nfs 192.168.0.101:*/*volume1/Synology /media/jjj/Synology
... that little "/" in front of 'volume1' could be important.
(2)
You might want to clean-up the exports list ...
... just to get started, put *only* the IP address f
On Mon, 11 Jul 2016 18:07:23 -0700
Don Buchholz dijo:
>(3) Try this command (as 'root'!) to see what the NAS is making
> available to mount with the NFS protocol:
>
> showmount -e 192.168.0.101
Export list for 192.168.0.101:
/volume1/Synology *.*.*.*,192.168.0.136,192.168.0.146,1
On Mon, 2016-07-11 at 18:07 -0700, Don Buchholz wrote:
showmount -e 192.168.0.101
Yes. Running this command (it may be /usr/sbin/showmount on your
machine) and posting the output will be helpful.
It looks to me as though the NAS isn't configured quite right. You need
to know what it thinks it'
(1) "only root can do that ..."
-- um, yes, generally, only 'root' is allowed to perform
mount(8) commands
-- so, you need to become 'root'
(a) login to the console as 'root', -OR-
(b) execute the command "su -" and enter root p/w
when prompted,
On Mon, 11 Jul 2016 18:04:41 -0500
David Fleck dijo:
>Forgive me if somebody has already posted this link:
>https://www.synology.com/en-us/knowledgebase/DSM/tutorial/File_Sharing/How_to_access_files_on_Synology_NAS_within_the_local_network_NFS
>
>Perhaps there is something in there that will clea
On Mon, 2016-07-11 at 12:30 -0700, John Jason Jordan wrote:
> jjj@Devil-Bonobo:/media/jjj$ mount -t nfs
> synology.local:/synology /media/jjj/Synology
> mount: only root can do that
> jjj@Devil-Bonobo:/media/jjj$ sudo su
> root@Devil-Bonobo:/media/jjj# mount -t nfs
> synology.l
On Mon, 11 Jul 2016 12:20:26 -0700
Bill Barry dijo:
>On Jul 11, 2016 11:48 AM, "John Jason Jordan"
>wrote:
>>
>> On Mon, 11 Jul 2016 17:41:30 +
>> Jason Spohn dijo:
>>
>> >Check out this page for some info on mounting NFS on Linux. Also
>> >shows how to create the proper 'fstab' to make it
On Mon, 11 Jul 2016 10:54:40 -0700
Don Buchholz dijo:
>> This is the command that mounts it with SMB:
>>
>> sudo mount.cifs //synology.local/synology/ /media/jjj/Synology/
>> --verbose -o user=jjj
>>
>> I assume I have to change either 'mount.cifs' or
>> '//synology.local/synology/. So far G
On Jul 11, 2016 11:48 AM, "John Jason Jordan" wrote:
>
> On Mon, 11 Jul 2016 17:41:30 +
> Jason Spohn dijo:
>
> >Check out this page for some info on mounting NFS on Linux. Also shows
> >how to create the proper 'fstab' to make it persistent.
> >http://www.tldp.org/LDP/nag2/x-087-2-nfs.mountd
On Mon, 11 Jul 2016 11:48:44 -0700, in message
2016074844.0a360442@Devil-Bonobo, John Jason Jordan wrote:
> On Mon, 11 Jul 2016 17:41:30 +
> Jason Spohn dijo:
>
> >Check out this page for some info on mounting NFS on Linux. Also
> >shows how to create the proper 'fstab' to make it persis
On Mon, 11 Jul 2016 17:41:30 +
Jason Spohn dijo:
>Check out this page for some info on mounting NFS on Linux. Also shows
>how to create the proper 'fstab' to make it persistent.
>http://www.tldp.org/LDP/nag2/x-087-2-nfs.mountd.html
I read the above page and tried what it said to do, but noth
On 7/11/2016 10:34 AM, John Jason Jordan wrote:
> On Sun, 10 Jul 2016 23:02:13 -0700
> Bill Barry dijo:
>
>> On Sun, Jul 10, 2016 at 10:42 PM, John Jason Jordan
>> wrote:
>>> I have discovered something that I should have noticed a long time
>>> ago, that is, that the entire drive is owned by roo
Jordan
Sent: Monday, July 11, 2016 10:34 AM
To: plug@lists.pdxlinux.org
Subject: Re: [PLUG] Rsync user confusion: Who is user 1026?
On Sun, 10 Jul 2016 23:02:13 -0700
Bill Barry dijo:
>On Sun, Jul 10, 2016 at 10:42 PM, John Jason Jordan
> wrote:
>> I have discovered something that I
On Sun, 10 Jul 2016 23:02:13 -0700
Bill Barry dijo:
>On Sun, Jul 10, 2016 at 10:42 PM, John Jason Jordan
> wrote:
>> I have discovered something that I should have noticed a long time
>> ago, that is, that the entire drive is owned by root. That would
>> explain the fact that the -o --owner and
On Sun, Jul 10, 2016 at 10:42 PM, John Jason Jordan
wrote:
> On Sat, 9 Jul 2016 22:42:04 -0700
> John Jason Jordan dijo:
>
> >But to test it I created a 0 byte file 'test' in the source folder, and
>
> I have discovered something that I should have noticed a long time ago,
> that is, that the en
On Sun, 10 Jul 2016 19:45:24 -0700
John Sechrest dijo:
>it there a reason you are not running it out of a root crontab?
Because I didn't know such a thing existed.
___
PLUG mailing list
PLUG@lists.pdxlinux.org
http://lists.pdxlinux.org/mailman/listinfo
On Sat, 9 Jul 2016 22:42:04 -0700
John Jason Jordan dijo:
>But to test it I created a 0 byte file 'test' in the source folder, and
>changed the * to test in the above command. At first the command failed
>with a permissions error (although I thought I had read that rsync does
>not require sudo),
it there a reason you are not running it out of a root crontab?
On Jul 10, 2016 6:17 PM, "John Jason Jordan" wrote:
> I have a command that does what I want, but that means it uses three
> options (-t --time, -o --owner, and -g --group), all three of which
> require root. Ultimately this will be
I have a command that does what I want, but that means it uses three
options (-t --time, -o --owner, and -g --group), all three of which
require root. Ultimately this will be run daily at 2am. Getting up at
2am to pump in my password is not going to happen.
According to the rsync man page adding
Having finally (!) mounted my new NAS drive I am working on rsync. I
have a prototype command:
rsync -rpt --delete /media/jjj/Movies/* /media/jjj/Synology
But to test it I created a 0 byte file 'test' in the source folder, and
changed the * to test in the above command. At first the command faile
On Sat, Jul 9, 2016 at 4:33 PM, John Jason Jordan
wrote:
> On Sat, 9 Jul 2016 13:39:54 -0700
> Bill Barry dijo:
>
> >With that knowledge the mount command would be closer to
> >
> >mount -t cifs //synology.local/synology/ /mnt --verbose -o
> >user=username
> >
> >where I still don't know the us
On Sat, 9 Jul 2016 13:39:54 -0700
Bill Barry dijo:
>With that knowledge the mount command would be closer to
>
>mount -t cifs //synology.local/synology/ /mnt --verbose -o
>user=username
>
>where I still don't know the username and /mnt should already exist or
>you need to create it.
I don't wan
On Sat, 9 Jul 2016, John Jason Jordan wrote:
> Then I decided to just move ahead to rsync and forget about cp, but I
> couldn't get rsync to see the Synology. I gave up for the time being.
John,
You need to mount it so the kernel sees it. As suggested by others, create
an entry for it in /etc
On Sat, Jul 9, 2016 at 1:39 PM, Bill Barry wrote:
>
>
> On Sat, Jul 9, 2016 at 1:34 PM, John Jason Jordan
> wrote:
>
>>
>>
>> I note that both rsync and mount are not seeing the Synology. It seems
>> to me that my big problem is giving the command line the right syntax
>> to specify it. It's IP
On Sat, Jul 9, 2016 at 1:34 PM, John Jason Jordan
wrote:
>
>
> I note that both rsync and mount are not seeing the Synology. It seems
> to me that my big problem is giving the command line the right syntax
> to specify it. It's IP address is 192.168.0.101 and Thunar shows it in
> the location bar
On Sat, 09 Jul 2016 11:35:46 -0700
Tomas Kuchta dijo:
>That (smb://..) will not work. you will need to mount your NAS
>into empty real directory on the filesystem - either on command line
>using mount (as root) or by adding it to /etc/fstab and letting the
>system mount it at boot for you.
>
On Sat, Jul 9, 2016 at 11:00 AM, John Jason Jordan
wrote:
>
> I'm out of ideas. Suggestions?
>
If you want to use cp you will have to mount the filesystem. The regular
mount command will do this. The filesystem type you want is called cifs.
The man page for the requisite options is here
man mou
On Sat, 2016-07-09 at 11:59 -0700, Rich Shepard wrote:
> On Sat, 9 Jul 2016, John Meissen wrote:
>
> > That's because 'cp' doesn't understand URL-style paths. 'cp' only deals
> > with local filesystems. If you want to use 'cp' you'll have to mount the
> > remote filesystem locally.
>
>Doesn't
On Sat, 9 Jul 2016, John Meissen wrote:
> That's because 'cp' doesn't understand URL-style paths. 'cp' only deals
> with local filesystems. If you want to use 'cp' you'll have to mount the
> remote filesystem locally.
Doesn't smb, like nfs, make the remote partitions accessible like local
part
That (smb://..) will not work. you will need to mount your NAS into empty
real directory on the filesystem - either on command line using mount (as root)
or by adding it to /etc/fstab and letting the system mount it at boot for you.
I understand from google that Thunar is some GUI file manag
On Sat, 9 Jul 2016 11:00:17 -0700, in message
20160709110017.3280e2bf@Devil-Bonobo, John Jason Jordan wrote:
> I can see I'm going to have to spend a lot of time studying rsync. But
> for starters I decided to use cp to see if I know how to specify the
> destination. Thunar displays a window with
joh...@comcast.net said:
> cp smb://synology.local/synology/ cp: cannot create regular
> file âsmb://synology.local/synology/â: No such file or directory
That's because 'cp' doesn't understand URL-style paths. 'cp' only deals with
local filesystems. If you want to use 'cp' you'll have to
On Sat, 2016-07-09 at 11:00 -0700, John Jason Jordan wrote:
> cp smb://synology.local/synology/
> cp: cannot create regular file ‘smb://synology.local/synology/’: No
> such file or directory
>
> I also tried it without the trailing slash and again with a slash
> in front and got the same results.
On Fri, 08 Jul 2016 23:55:16 -0700
Tomas Kuchta dijo:
>if you add rsync --delete option then rsync will delete remote files
>as you describe. For the safety of your files, maybe you should
>consider enabling snapshots or do some safeguarding with your mirror
>scripts.
>
>It would be unfortunate t
if you add rsync --delete option then rsync will delete remote files as you
describe. For the safety of your files, maybe you should consider enabling
snapshots or do some safeguarding with your mirror scripts.
It would be unfortunate to loose all the NAS backup files just because you
accidenta
I have just successfully set up a Synology DiskStation NAS device with
one 6TB drive on my home ethernet. This was not a trivial matter, as
I had never done this before and I know little about networking.
I also have a 5TB USB 3.0 drive attached to my laptop with presently
~3TB of files on it. I
On Sat, 20 Jun 2015, Dale Snell wrote:
> Argh... I meant the _source_ directory. (*sigh* not enough coffee.) The
> remote host's path has to be absolute, or rsync won't know where subdir
> and its files are.
Dale,
And that's what I provided (c.f. original post): 'rsync -avz
srchost:/directo
On Sat, 20 Jun 2015 07:11:48 -0700 (PDT), in message
alpine.LNX.2.11.1506200708210.8143@localhost, Rich Shepard wrote:
> On Sat, 20 Jun 2015, Dale Snell wrote:
>
> > If memory and my interpretation of the man page are correct (and
> > neither may be, I've not had my morning caffeine yet), rsync
>
On Sat, 20 Jun 2015, Dale Snell wrote:
> If memory and my interpretation of the man page are correct (and neither
> may be, I've not had my morning caffeine yet), rsync requires you to
> specify an absolute path for the destination. Hence
>
> rsync -avz host:/path/to/dir/subdir/ .
>
> should work
On Sat, 20 Jun 2015 05:44:24 -0700 (PDT), in message
alpine.LNX.2.11.1506200539350.8143@localhost, Rich Shepard wrote:
>A question for you professional admins: what situation might
> result in the command, 'rsync -avz host:directory/subdirctory/ .'
> reporting that the directory/subdirectory d
A question for you professional admins: what situation might result in the
command, 'rsync -avz host:directory/subdirctory/ .' reporting that the
directory/subdirectory does not exist on that host while the command, 'scp
host:directory/subdirctory/* .' work like a charm?
If I neglected to sp
On Mon, 15 Apr 2013, Paul Mullen wrote:
> In my experience, rsync is best for one-way file system
> synchronizations (i.e., mirroring). If both file systems are likely
> to change (e.g., a desktop and laptop that both see frequent use),
> then I highly recommend Unison.
Thanks, Paul. I daily
On Mon, Apr 15, 2013 at 03:52:30PM -0700, Rich Shepard wrote:
> I was under the impression that rsync did not overwrite a newer file with
> an older file, but that's what just happened. I'd like to understand what I
> did incorrectly so I can avoid this mistake in the future.
In my experience, rsy
On Mon, 15 Apr 2013, Ronald Chmara wrote:
> NTP can be your friend. I've seen huge amounts of borkage because of clock
> drift, and some distros that don't enable it by default, so machines are
> off by 8-12 hours(!) after only a couple of weeks.
Ronabop,
ntpd runs on the laptop as well as on
On Mon, Apr 15, 2013 at 4:21 PM, Robert Citek wrote:
> On Mon, Apr 15, 2013 at 6:52 PM, Rich Shepard
> wrote:
> ...
> > rsync -avz * salmo:documents/workshop-presentations/nada-talk/
> ...
> >What rsync syntax error did I commit?
> Sounds like you wanted the --update option:
> -u, --
On Mon, 15 Apr 2013, Robert Citek wrote:
> Sounds like you wanted the --update option:
>
> -u, --updateskip files that are newer on the receiver
Robert,
Oh. I don't recall using that option before; perhaps I've forgotten that I
did add the 'u' to the option string when I've do
On Mon, Apr 15, 2013 at 6:52 PM, Rich Shepard wrote:
...
> rsync -avz * salmo:documents/workshop-presentations/nada-talk/
...
>What rsync syntax error did I commit?
Sounds like you wanted the --update option:
-u, --updateskip files that are newer on the receiver
So
I was under the impression that rsync did not overwrite a newer file with
an older file, but that's what just happened. I'd like to understand what I
did incorrectly so I can avoid this mistake in the future.
While I was on a business trip last week I created new files in a
subdirectory on t
Russell Johnson wrote:
> On Aug 2, 2011, at 9:17 AM, Roderick A. Anderson wrote:
>
>>rsync -azrR --include-from=/var/backup.d/svr1.lst /mnt/backup/svr1/
>
> My standard rsync incantation is:
>
> rsync -rvca --delete-after --progress /source/dir/path /destination/dir/path
Thanks.
I'll give
On Aug 2, 2011, at 9:17 AM, Roderick A. Anderson wrote:
>rsync -azrR --include-from=/var/backup.d/svr1.lst /mnt/backup/svr1/
My standard rsync incantation is:
rsync -rvca --delete-after --progress /source/dir/path /destination/dir/path
Other options (hostname, ssh, etc.) are used when appr
I'm trying to come up with the correct command line parameters to do
what should be (I think) a pretty simple rsync backup/copy to another
directory.
The tricky parts seem to be how to preserve the "sub-"directory
structure for each sub-directory. Clear as mud ... right?
What I'm confined by
On 04/27/2011 04:30 PM, Keith Lofstrom wrote:
> On Wed, Apr 27, 2011 at 12:00:47PM -0700, Bruce Kilpatrick wrote:
>> All,
>>
>> I have been playing around with rsync getting ready to upgrade to
>> Natty. I have an encrypted /home and some reading suggests that
>> occasional failures happen to the
On Wed, Apr 27, 2011 at 12:00:47PM -0700, Bruce Kilpatrick wrote:
> All,
>
> I have been playing around with rsync getting ready to upgrade to
> Natty. I have an encrypted /home and some reading suggests that
> occasional failures happen to the home partition during installation.
>
> I put tog
On 04/27/2011 02:22 PM, chris (fool) mccraw wrote:
> On Wed, Apr 27, 2011 at 12:00, Bruce Kilpatrick wrote:
>
>> The question is which of the dot files are really necessary to keep, and
>> will it save much room if they are not copied?
> browser (and acrobat reader) cache are typically my biggest
On Wed, Apr 27, 2011 at 12:00, Bruce Kilpatrick wrote:
> The question is which of the dot files are really necessary to keep, and
> will it save much room if they are not copied?
browser (and acrobat reader) cache are typically my biggest "hidden"
files. here's how you can tell what's worth inv
All,
I have been playing around with rsync getting ready to upgrade to
Natty. I have an encrypted /home and some reading suggests that
occasional failures happen to the home partition during installation.
I put together a script sometime back and the external hard drive is now
full. Have del
On 06/29/2010 06:58 PM, Nathan W wrote:
> posting this here in the hope someone may catch something i'm missing.
>
> i'm trying to teach myself rsync, as the other backup solutions i'd been
> using don't do diff's, and thus take too long to backup. i've come up w/
> a functional backup to backup fr
Nathan W wrote:
> On 06/29/2010 06:58 PM, Nathan W wrote:
>
>> posting this here in the hope someone may catch something i'm missing.
>>
>> i'm trying to teach myself rsync, as the other backup solutions i'd been
>> using don't do diff's, and thus take too long to backup. i've come up w/
>> a fu
On 06/29/2010 06:58 PM, Nathan W wrote:
> posting this here in the hope someone may catch something i'm missing.
>
> i'm trying to teach myself rsync, as the other backup solutions i'd been
> using don't do diff's, and thus take too long to backup. i've come up w/
> a functional backup to backup fr
posting this here in the hope someone may catch something i'm missing.
i'm trying to teach myself rsync, as the other backup solutions i'd been
using don't do diff's, and thus take too long to backup. i've come up w/
a functional backup to backup from my laptop to our home network server,
but i
Bruce KIlpatrick wrote:
> Kris wrote:
>> Bruce KIlpatrick wrote:
>>> I have been working to learn a bit about rsync, in preperation for
>>> upgrading to Jaunty. After reading several tutorials, reading some of
>>> the man page, and generally messing around with some minor changes in
>>> syntax,
Kris wrote:
> Bruce KIlpatrick wrote:
>> I have been working to learn a bit about rsync, in preperation for
>> upgrading to Jaunty. After reading several tutorials, reading some of
>> the man page, and generally messing around with some minor changes in
>> syntax, I came up with the following.
Bruce KIlpatrick wrote:
> I have been working to learn a bit about rsync, in preperation for
> upgrading to Jaunty. After reading several tutorials, reading some of
> the man page, and generally messing around with some minor changes in
> syntax, I came up with the following.
I'll chime in abo
Michael M. Moore wrote:
> On Tue, 2009-06-02 at 08:18 -0700, Bruce KIlpatrick wrote:
>> The only error I see in the log file at this point is a permission
>> denied at /home/robin/.config/menus so adding an --exclude would not be
>> a problem.
>>
>> After thinking about this a little more...besid
On Tue, 2009-06-02 at 08:18 -0700, Bruce KIlpatrick wrote:
>
> The only error I see in the log file at this point is a permission
> denied at /home/robin/.config/menus so adding an --exclude would not be
> a problem.
>
> After thinking about this a little more...besides wanting to "learn to
>
Paul Mullen wrote:
> On Mon, Jun 01, 2009 at 10:17:07PM -0700, Bruce KIlpatrick wrote:
>> #!bin/bash
>> sudo rsync -av --progress --delete
>> --log-file=/home/bruce/Desktop/$(date +%Y%m%d)_moose_rsync.log
>> ro...@xxx.xxx.xx.xxx:/home/robin /media/disk/MooseBackup
>
> I usually include "-x", w
On Mon, Jun 01, 2009 at 10:17:07PM -0700, Bruce KIlpatrick wrote:
> #!bin/bash
> sudo rsync -av --progress --delete
> --log-file=/home/bruce/Desktop/$(date +%Y%m%d)_moose_rsync.log
> ro...@xxx.xxx.xx.xxx:/home/robin /media/disk/MooseBackup
I usually include "-x", which instructs rsync to not c
I have been working to learn a bit about rsync, in preperation for
upgrading to Jaunty. After reading several tutorials, reading some of
the man page, and generally messing around with some minor changes in
syntax, I came up with the following.
#!bin/bash
sudo rsync -av --progress --delete
87 matches
Mail list logo
