On Tue, Jul 09, 2024 at 11:37:19AM GMT, BP25 via rsync wrote:
> In other words, the recursion did not happen linearly (according to
> the tree structure of either the sender or the receiver). This is
> very counter-intuitive: I'd expect that every line which lies
> between any two lines of the
Also note the SORTED TRANSFER ORDER paragraph in the rsync
manual. I don't think this paragraph is relevant to my question because
I understand it's only relevant to multiple nonrecursive rsync commands;
whereas I have one single recursive rsync command.
--
Please use reply-all for most
The only explanation I can find for such behaviour is that
incremental recursion is being used, which leads me to deduce that the
lines with path outside of the directory "A/B/...", can only indicate
folder creation. But yet I cannot buy this explanation because why would
such "atypical
Dear rsync community,
I hope that someone can help me with this issue, probably
related to my lack of understanding of how rsync recursive works. In the
output was displayed something like this (I don't remember in the lines
below whether rsync was deleting or creating files
https://bugzilla.samba.org/show_bug.cgi?id=5482
Wayne Davison changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
leonv12 via rsync wrote:
> I don't get why it runs from the command line but not from a scheduled
> task. Any suggestions for a fix or a work-around?
Check the environment settings, which are often the cause of differences
in behavior between running from the command
On Sat, 29 Jul 2017 19:45:22 -0700 (PDT)
leonv12 via rsync wrote:
> I don't get why it runs from the command line but not from a
> scheduled task. Any suggestions for a fix or a work-around?
Talk to someone who knows about task scheduling and its
failure modes?
Karl
I don't get why it runs from the command line but not from a scheduled task.
Any suggestions for a fix or a work-around?
--
View this message in context:
http://samba.2283325.n4.nabble.com/Help-rsync-runs-from-command-line-fails-from-task-scheduler-hangs-at-msg-checking-charset-UTF-8
d/receive (code 30) at
> io.c(195) [sender=3.1.2][sender] _exit_cleanup(code=30, file=io.c,
> line=195): about to call exit(30)Help will be much appreciated!
Reminds me of previous struggles I've had with MS Windows and
byte order marks. (Something about the way it requires UTF-16
but bre
nc_partial .
/data/current/systemID/cygdrive/c (18 args)*msg checking charset:
UTF-8*[sender] io timeout after 3000 seconds -- exiting[sender]
_exit_cleanup(code=30, file=io.c, line=195): enteredrsync error: timeout in
data send/receive (code 30) at io.c(195) [sender=3.1.2][sender]
_exit_cleanup(
https://bugzilla.samba.org/show_bug.cgi?id=12217
Bug ID: 12217
Summary: pogo games @1800-790-9186 support customer service
phone number,support help desk phone number
Product: rsync
Version: 3.1.3
Hardware: All
... no
checking for library containing libiconv_open... no
...
$ make
...
$ ./rsync.exe --help |grep iconv
append, no ACLs, no xattrs, no iconv, symtimes, prealloc
How i can say configure about libiconv?
Laboratory of Medical Ultrasound Devices
Scientific Department
SPbSPU
--
Please use
... no
checking for library containing libiconv_open... no
...
$ make
...
$ ./rsync.exe --help |grep iconv
append, no ACLs, no xattrs, no iconv, symtimes, prealloc
How i can say configure about libiconv?
--
Best regards,
Roman Romanovskiy
+79217447768
+78122909636
Laboratory of Medical
fix.
>
> I included a reproducer script and a patch that worked well for me, but as
> this is the first time I've looked at the rsync code base I wouldn't be too
> surprised if I'd missed some portability implications or the like.
>
> I was wondering if there's anything further
at the rsync code base I wouldn't be too
surprised if I'd missed some portability implications or the like.
I was wondering if there's anything further I could do to help.
Thanks,
-mike
[1]: https://bugzilla.samba.org/show_bug.cgi?id=11521
--
Please use reply-all for most replies to avoid omitting
https://bugzilla.samba.org/show_bug.cgi?id=10389
Summary: Sort the output of --help into alphabetical order
Product: rsync
Version: 3.1.1
Platform: All
OS/Version: All
Status: NEW
Severity: normal
Priority: P5
On Tue, Aug 27, 2013 at 8:03 PM, Sherin A sherin...@gmail.com wrote:
Hope they will report it as a vulnerability , because this POC has been
exploited successfully and it is affected by all software that use rsync
as a backup and restore tool.
This is totally false. The vulnerability
On Thursday 29 August 2013 11:46 PM, Wayne Davison wrote:
On Tue, Aug 27, 2013 at 8:03 PM, Sherin A sherin...@gmail.com
mailto:sherin...@gmail.com wrote:
Hope they will report it as a vulnerability , because this POC
has been exploited successfully and it is affected by all
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chown itself is not insecure. The indiscriminate chowning of all
files creates security issues.
You can use --fake-super on push backups. In fact that is what
- --fake-super is DESIGNED FOR. You just have to make sure that
- --fake-super is
The solution is not to refuse to backup any file that is a hard link.
There are legitimate reasons to have hard links and ignoring them
means you aren't backing up everything.
I agree that preserving hard links may be important in some situation. There
are certainly legitimate reasons to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
My opinion on backups is pretty simplistic. If a restore of my backup
doesn't bring me back to what I had when I backed up then I don't have
a backup.
If I have to restore something and the relationship between files that
were hard linked in the
On Wednesday 28 August 2013 04:14 AM, Kevin Korb wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
My opinion on backups is pretty simplistic. If a restore of my backup
doesn't bring me back to what I had when I backed up then I don't have
a backup.
If I have to restore something and the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Only when you choose to force a completely unnecessary chown between
the backup and restore process.
On 08/27/13 23:03, Sherin A wrote:
On Wednesday 28 August 2013 04:14 AM, Kevin Korb wrote: My opinion
on backups is pretty simplistic. If a
On Wednesday 28 August 2013 08:36 AM, Kevin Korb wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Only when you choose to force a completely unnecessary chown between
the backup and restore process.
On 08/27/13 23:03, Sherin A wrote:
On Wednesday 28 August 2013 04:14 AM, Kevin Korb wrote:
in the rsync man to copy only
each users files , can you please point me to that
option
Thanking you for your valuable time and help .
So, It need to be a pull type rsync with unprivileged user ?. It
was not a permanent solution always. May be it is the time to
present this POC
each user's files and only their files.
I don't see an option in the rsync man to copy only each
users files , can you please point me to that option
Thanking you for your valuable time and help
for rsync for excluding hardlinks with -links +1 links ,
please help me , it is easy to check the file with an lstat / stat
system call. Or is it possible to get a developer documentation for
rsync with the detailed info ?
You could do that with --exclude, but first, think about
with -links +1 links ,
please help me , it is easy to check the file with an lstat / stat
system call. Or is it possible to get a developer documentation for
rsync with the detailed info ?
You could do that with --exclude, but first, think about the
implications of that. Your users could make hardlinks
with
-links +1 links , please help me , it is easy to check the
file with an lstat / stat system call. Or is it possible
to get a developer documentation for rsync with the
detailed info ?
You could do that with --exclude, but first, think about the
implications of that. Your users could
valuable time and help .
--
--
Regards
Sherin A
http://www.sherin.co.in/
--
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http
to that option
Thanking you for your valuable time and help .
- --
~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~
Kevin Korb Phone:(407) 252-6853
Systems Administrator Internet:
FutureQuest, Inc
know.
B) backing up each user's files and only their files.
I don't see an option in the rsync man to copy only each users
files , can you please point me to that option
Thanking you for your valuable time and help
user's files and only their files.
I don't see an option in the rsync man to copy only each
users files , can you please point me to that option
Thanking you for your valuable time and help
user's files and only their files.
I don't see an option in the rsync man to copy only each
users files , can you please point me to that option
Thanking you for your valuable time and help .
- --
~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~
Kevin Korb
]#
If I am doing something wrong please let me know.
B) backing up each user's files and only their
files.
I don't see an option in the rsync man to copy only
each users files , can you please point me to that
option
Thanking you for your valuable time and help
On Tuesday 13 August 2013 12:23 PM, Joe wrote:
Is there any way at all to say which is the original file and which is
the hard link? I'll bet there isn't, although I' m not an internals guy
at all. If so, this would be impossible to do. The inode is the
original, but all the file table
I'm going to give this one more shot and then wait for the experts to
weigh in.
I'll stick with your example of /etc/shadow, but this applies to any
secured file on the system.
On my system /etc/shadow is 640 (by default), so, as a normal user, I
can't even see it (other than to see that it
On Tue 13 Aug 2013, Sherin A wrote:
But if a user create a
hard link to /etc/shadow from his home dir , and he request a restore ,
then he can read the shadow files and decrypt it .
If he can make a HARD link to the shadow file, then he can already read
it - and worse.
Paul
--
Please use
Hello Joe,
Thanks for your reply . But think about the real world users. There
is not always necessary the /home will be in separate disk partition or
/tmp , /var/tmp , /usr/tmp. Think about an openvz vps or disk with
everything on / (most of the cloud servers) . Rsync is using in
On 13.08.2013 09:52, Paul Slootman wrote:
On Tue 13 Aug 2013, Sherin A wrote:
But if a user create a
hard link to /etc/shadow from his home dir , and he request a restore ,
then he can read the shadow files and decrypt it .
If he can make a HARD link to the shadow file, then he can
On Tue 13 Aug 2013, Matthias Schniedermeyer wrote:
On 13.08.2013 09:52, Paul Slootman wrote:
On Tue 13 Aug 2013, Sherin A wrote:
But if a user create a
hard link to /etc/shadow from his home dir , and he request a restore ,
then he can read the shadow files and decrypt it .
If
On Tue 13 Aug 2013, Matthias Schniedermeyer wrote:
BUT there is no direct vulnerability in that, only processes after that
(like backup/rsync) can make a vulnerability out of it.
... which is what I already wrote.
Paul
--
Please use reply-all for most replies to avoid omitting the mailing
On 13.08.2013 14:18, Paul Slootman wrote:
On Tue 13 Aug 2013, Matthias Schniedermeyer wrote:
Hardlinking a file doesn't change it's owner/group/permission
(All Hardlinks have the same user/group/permissions).
I never said that.
You implied that by your assertion that you
On 13.08.2013 14:20, Paul Slootman wrote:
On Tue 13 Aug 2013, Matthias Schniedermeyer wrote:
BUT there is no direct vulnerability in that, only processes after that
(like backup/rsync) can make a vulnerability out of it.
... which is what I already wrote.
I read your sentence
On Tue 13 Aug 2013, Matthias Schniedermeyer wrote:
I read your sentence differently:
If he can make a HARD link to the shadow file, then he can already
read it - and worse.
My understanding of your sentence says:
The ability to hardlink, means that anyone can read any file they can
On 13.08.2013 15:51, Paul Slootman wrote:
On Tue 13 Aug 2013, Matthias Schniedermeyer wrote:
I read your sentence differently:
If he can make a HARD link to the shadow file, then he can already
read it - and worse.
My understanding of your sentence says:
The ability to
On Tuesday 13 August 2013 05:50 PM, Paul Slootman wrote:
On Tue 13 Aug 2013, Matthias Schniedermeyer wrote:
BUT there is no direct vulnerability in that, only processes after that
(like backup/rsync) can make a vulnerability out of it.
... which is what I already wrote.
Paul
So the solutions
On Tuesday 13 August 2013 07:51 PM, Matthias Schniedermeyer wrote:
On 13.08.2013 15:51, Paul Slootman wrote:
On Tue 13 Aug 2013, Matthias Schniedermeyer wrote:
I read your sentence differently:
If he can make a HARD link to the shadow file, then he can already
read it - and worse.
My
On 13.08.2013 20:44, Sherin A wrote:
On Tuesday 13 August 2013 05:50 PM, Paul Slootman wrote:
On Tue 13 Aug 2013, Matthias Schniedermeyer wrote:
BUT there is no direct vulnerability in that, only processes after that
(like backup/rsync) can make a vulnerability out of it.
... which is what I
On Tuesday 13 August 2013 08:56 PM, Matthias Schniedermeyer wrote:
On 13.08.2013 20:44, Sherin A wrote:
On Tuesday 13 August 2013 05:50 PM, Paul Slootman wrote:
On Tue 13 Aug 2013, Matthias Schniedermeyer wrote:
BUT there is no direct vulnerability in that, only processes after that
(like
there
kernel to 3.6
Matthias already pointed out that the changed default behavior in
new kernel is meant to help users avoid shooting themselves in the
foot, but doesn't implement added security. In particular, it doesn't
fix pre-existing hardlinks created by users who can't read the file;
indeed
file instead of waiting the OS vendors for updating there
kernel to 3.6
Matthias already pointed out that the changed default behavior in
new kernel is meant to help users avoid shooting themselves in the
foot, but doesn't implement added security. In particular, it doesn't
fix pre-existing
On Tue, Aug 13, 2013 at 09:43:06PM +0530, Sherin A wrote:
If linux user foo , with home /home/foo , what ownership we need
to give the files under his home folder , it must be foo and not
root.
Why? The user created the hardlink themselves, and it had root
ownership, why should the
On 13.08.2013 21:04, Sherin A wrote:
On Tuesday 13 August 2013 08:56 PM, Matthias Schniedermeyer wrote:
On 13.08.2013 20:44, Sherin A wrote:
On Tuesday 13 August 2013 05:50 PM, Paul Slootman wrote:
On Tue 13 Aug 2013, Matthias Schniedermeyer wrote:
BUT there is no direct vulnerability in
: if any one interested in making a patch with an additional option
for rsync for excluding hardlinks with -links +1 links , please help
me , it is easy to check the file with an lstat / stat system call.
Or is it possible to get a developer documentation for rsync with the
detailed info
,
please help me , it is easy to check the file with an lstat / stat
system call. Or is it possible to get a developer documentation for
rsync with the detailed info ?
You could do that with --exclude, but first, think about the
implications of that. Your users could make hardlinks to system
). That way you get proper, original-owner restores.
PS : if any one interested in making a patch with an additional option for
rsync for excluding hardlinks with -links +1 links , please help me
This is not something I'll be looking into, FYI.
..wayne..
--
Please use reply-all for most replies
Can some one create a patch for excluding hard link regular file from
copying ?. May be like a command flag , rsync --no-hardlink-copy
--
--
Regards
Sherin A
http://www.sherin.co.in/
--
Please use reply-all for most replies to avoid omitting the
On Sat, Jul 6, 2013 at 11:33 PM, Garvit Sharma garvit...@gmail.com wrote:
*rsync -av --files-from=FILE --delete-before src/ dest/*
For rsync's --delete to do anything, you must send an entire directory of
files, e.g. if you added -r to that command and specified a directory in
the files-from
Hello All,
*rsync -av --files-from=FILE --delete-before src/ dest/*
the above mentioned command not working. I want to delete extra files on
the dest that are not on the source and transferring the selected files
from FILE simultaneously. Please suggest me how to do that ??
--
Regards
Garvit
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
- --delete and --files-from don't work together.
- --files-from is for specifying an exact list of what to copy.
Therefore there can't be anything to delete because there is nothing
it looks at other than the specified list.
Also, never ever use
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
OK, I didn't notice the * at the beginning of the command. Yes, when
I look at your original message I see a bolded command. I got the
stars when I replied because my thunderbird is configured to always
compose in plain text unless I tell it
If you really want to exclude /vault/test1/ccc, and for /vault/test2
to end up at /store/test2, then I would suggest:
rsync -avz --exclude /test1/ccc src:/vault/ dest:/store
rsync -avz src:/vault/test2 dest:/store
that runs rsync over ssh.
Note that the trailing slash on the src argument in the
Hi mate,
Thanks for your reply. However, I think there's more common scenario I
will encounter.
SRC:
dir: /vault/test1
file: /vault/test1/aaa
file: /vault/test1/bbb
file: /vault/test1/ccc
dir: /vault/test2
dir: /vault/test3
dir: /vault/test4
dir: ...
file: ...
DEST:
dir: /store
file:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
rsync -vai --exclude=ccc/ --delete /valut/test[12] dest:/store/
On 02/10/13 11:19, Lee Eric wrote:
Hi mate,
Thanks for your reply. However, I think there's more common
scenario I will encounter.
SRC:
dir: /vault/test1 file:
https://bugzilla.samba.org/show_bug.cgi?id=9211
--- Comment #1 from mlus...@redhat.com 2012-10-02 09:01:22 UTC ---
Created attachment 7976
-- https://bugzilla.samba.org/attachment.cgi?id=7976
patch
--
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
--- You are
https://bugzilla.samba.org/show_bug.cgi?id=9211
Summary: Inconsistency between man page and help
Product: rsync
Version: 3.0.9
Platform: All
OS/Version: All
Status: NEW
Severity: normal
Priority: P5
the latest version of rsync up and
running.
Any help anyone would be kind enough to provide would be much appreciated.
Thanks,
S.N.
--
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
of getting the latest version of rsync up and
running.
Any help anyone would be kind enough to provide would be much appreciated.
Thanks,
S.N.
--
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options:
https://lists.samba.org
Hello,
Thanks. I appreciate the help. I'd never have figured out those steps
on my own (not a guru yet...). I was hoping to avoid completely anything from
Apple's Developer Tools, but, apparently, this is not possible.
Just to verify two things:
(1) Once your instructions have been followed
install
ciao!
Banana
On May 8, 2012, at 4:25 PM, s.no...@free.fr wrote:
Hello,
Thanks. I appreciate the help. I'd never have figured out those steps
on my own (not a guru yet...). I was hoping to avoid completely anything from
Apple's Developer Tools, but, apparently, this is not possible
it with the same step:
./configure
make
sudo make install
ciao!
Banana
Hello,
Thanks. I appreciate the help. I'd never have figured out those steps
on my own (not a guru yet...). I was hoping to avoid completely anything
from
Apple's Developer Tools
On Thu, 22 Mar 2012 17:48:44 +0100, Paul Slootman wrote:
--fuzzy aside, I'm a great believer of logrotate's dateext option.
So am I, and not just for backups. It's easier to find the log file one
needs with datestamps.
Unfortunately, that machine not using it isn't my machine to administer.
I've identified a situation where the combination of --fuzzy --fuzzy
(yes: two of them) and --link-dest is not behaving as I'd expect. I'm
first wondering if my expectation is wrong. Assuming that it is not,
then I'm wondering how best to figure out the problem.
The double use of --fuzzy is
On Thu, 22 Mar 2012 14:23:13 +, Andrew Gideon wrote:
Assuming my expectation is correct, and that --fuzzy should have an
effect in this case, I'm wondering how best to test what's occurring.
I've tried using --itemize-changes in a --dry-run, but all it tells me
is f.st.. which is what
On Thu 22 Mar 2012, Andrew Gideon wrote:
Note that the source ads_live_error.log.9.gz would not match the
destination HOLD.ads_live_error.log.9.gz. Instead, it should have
matched the destination ads_live_error.log.10.gz. I mention this in case
that plays a role in this failure.
You want --exclude-from=file
You can cut-and-paste those path patterns into that file just as they are.
Sadly, I'm still getting the files on the destination.
Any ideas? 3.0.7 on windows, 3.0.8 on mac.
--
Political and economic blog of a strict constitutionalist
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The two most common problems with excludes are:
1. Excluded paths are relative to the source path. So if you are
rsyncing /home/username and you want to exclude /home/username/Trash
the path to exclude is actually /Trash.
2. Mistaking the fact that
2. Mistaking the fact that the files are in the target because they
were already in the target for rsync actually transferring them. If
they were there before you ran rsync they will still be there after
unless you use --delete-excluded
Whoops! I thought that was the default. Thank you.
--
at excludes.
e.g.
$ rsync -zav $HOME/phildobbin/ --exclude 'foo/' /destination/backup/
which works perfectly well but I'm struggling to find the right syntax
to add about another half a dozen directories to the exclude list (e.g.
Movies/ Music/ Virtualbox/ so on).
Any help appreciated.
Cheers
perfectly well but I'm struggling to find the right
syntax to add about another half a dozen directories to the exclude
list (e.g. Movies/ Music/ Virtualbox/ so on).
Any help appreciated.
Cheers,
Phil
On Sat, 2011-12-24 at 20:20 -0500, Kevin Korb wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
- --exclude Movies/ --exclude Music/
Or put them in a text file list and use --exlcude-from
Many thanks. Happy holidays...
Cheers,
Phil.
--
Please use reply-all for most replies to
I apologize in advance for asking a beginner question, but I really
could not figure this from the manual page.
I want to copy some files with rsync, and not copy others.
The stuff that I do not want to copy looks like this:
System Volume Information/_restore*/RP*
WINDOWS/Prefetch/*
Documents
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
You want --exclude-from=file
You can cut-and-paste those path patterns into that file just as they are.
For the ACL errors you are probably writing to a filesystem that
doesn't support those ACLs.
On 12/18/11 13:58, Michael_google gmail_Gersten
I'm trying to use rsync to copy files from a Microsoft Windows machine
(XP, with cygwin) to a macintosh (10.5.8, PPC).
After a lot of playing with options, manual page reading, etc, I have
the following command, executed on the windows machine:
rsync -A -X -a --delete
Hello,
2010/11/15 17:40:32 [3200] rsync: writefd_unbuffered failed to write 8 bytes
[generator]: Broken pipe (32)
2010/11/15 17:40:32 [3200] rsync error: error in rsync protocol data stream
(code 12) at io.c(1550) [generator=3.0.4]
What's mean this log ??
Thanks!
--
Please use reply-all for
Hi,
This error could probably come from the drop of an unstable network connection.
Check my recent post about it:
http://www.mail-archive.com/rsync@lists.samba.org/msg26280.html
In my case, the solution was to use rsync over a ssh tunnel. The ssh tunnel is
more robust about network problems
On Thu, 2010-01-21 at 09:55 +0200, Yan Valuyskiy wrote:
I believe for this you'll have to provide a kind of next include file
with --files-include option:
Thank you. What is the full string for the [OPTION --file-include
option], saying the file name below is rsync.list.
My understanding was
I can not get it to work
http://pastebin.com/f432bf596
On Thu, 2010-01-21 at 18:05 +0900, nomnex wrote:
On Thu, 2010-01-21 at 09:55 +0200, Yan Valuyskiy wrote:
I believe for this you'll have to provide a kind of next include file
with --files-include option:
Thank you. What is the
Yan,
I might be tired from repeated tries. It still fail.
m...@fmv:~$ rsync -rvt --include-from=rsyncfinal /home /home/rsynctest
sending incremental file list
[sender] hiding directory home because of pattern **
delta-transmission disabled for local transfer or --whole-file
total:
Hi,
Linux-Ubuntu here. English is not my first language. The man rsync is
difficult to understand. I want to backup some folders recursively and
some files, see [1] in my /home dir to an external USB HD (Ext4). I want
to use a text file for the purpose.
[1]
/home/user/Documents
see /mnt/Data/backup/USB_HDD_4/*.*)
folder and then everything is under that folder. What command can I run so
its directly under the backkup folder (/mnt/Data/backup/*.*)?
rsync -e ssh -p 2223 -avz --delete-after /USB/USB_HDD_4
u...@1.1.1.1:/mnt/Data/backup
Thanks in advance for the help
/USB_HDD_4/*.*) folder
and then everything is under that folder. What command can I run so its
directly under the backkup folder (/mnt/Data/backup/*.*)?
rsync -e ssh -p 2223 -avz --delete-after /USB/USB_HDD_4
u...@1.1.1.1:/mnt/Data/backup
Thanks in advance for the help.
--
View this message
Hi,
I tried to send bash file via rsync from Ubuntu server to FreeBSD server
I configure the FreeBSD as rsync server. The rsync daemon is running.
I install rsync 3.0.6 on bought servers
furst I type on Ubuntu
rsync /home/rcbandit/buffer.sh
rcban...@192.168.1.106:/home/rcbandit/
The
Thanks Matt, that was great information.
I think I don't need to use exclude at all and just need to user H and P
flags with --filter option. Also I will need to use --delete option to
remove directories filtered H flag. The below command meets exactly my
requirements:
rsync -avz /foo/bar/
Matt McCutchen (m...@mattmccutchen.net) wrote on 26 July 2009 17:45:
On Sun, 2009-07-26 at 21:37 +0530, Jignesh Shah wrote:
I have a situation where I want to delete some of my excluded patterns
but still want to preserve some other. For example consider below
source and destination
Yup, it is working.
On Mon, Jul 27, 2009 at 7:42 PM, Carlos Carvalho car...@fisica.ufpr.brwrote:
Matt McCutchen (m...@mattmccutchen.net) wrote on 26 July 2009 17:45:
On Sun, 2009-07-26 at 21:37 +0530, Jignesh Shah wrote:
I have a situation where I want to delete some of my excluded
Hi,
I have a situation where I want to delete some of my excluded patterns but
still want to preserve some other. For example consider below source and
destination directory hierarchy.
SourceDest
-- -
/foo/bar/ /foo/bar/
On Sun, 2009-07-26 at 21:37 +0530, Jignesh Shah wrote:
I have a situation where I want to delete some of my excluded patterns
but still want to preserve some other. For example consider below
source and destination directory hierarchy.
SourceDest
--
help very much appreciated.
Please include me on any replies as I'm not subscribed to this list.
Regards,
Tom
Sorry to pick this up again - wondering if anyone has any ideas or can
suggest a way to debug this problem? No one on the #rsync IRC channel
is able to explain this either...
Tom
1 - 100 of 490 matches
Mail list logo