https://bugzilla.samba.org/show_bug.cgi?id=3253
[EMAIL PROTECTED] changed:
What|Removed |Added
Severity|normal |enhancement
Status|NEW
https://bugzilla.samba.org/show_bug.cgi?id=3253
--- Comment #2 from [EMAIL PROTECTED] 2005-11-16 18:51 MST ---
Created an attachment (id=1575)
-- (https://bugzilla.samba.org/attachment.cgi?id=1575action=view)
perl script solution
I enjoy coding simple perl scripts like this, so
https://bugzilla.samba.org/show_bug.cgi?id=3271
Summary: Rsync instances stay in memory when using in daemon mode
Product: rsync
Version: 2.6.7
Platform: x86
OS/Version: Linux
Status: NEW
Severity: normal
Priority:
https://bugzilla.samba.org/show_bug.cgi?id=3271
--- Comment #1 from [EMAIL PROTECTED] 2005-11-18 06:21 MST ---
Created an attachment (id=1580)
-- (https://bugzilla.samba.org/attachment.cgi?id=1580action=view)
log file of strace, log file of rsync and log.c file
--
Configure
https://bugzilla.samba.org/show_bug.cgi?id=3186
--- Comment #1 from [EMAIL PROTECTED] 2005-11-22 14:16 MST ---
Any ideas on this? It's been open 5 weeks and probably got overlooked... Tnx!
--
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
--- You are
https://bugzilla.samba.org/show_bug.cgi?id=3277
Summary: [Feature req] I couldn't do something you asked
warning
Product: rsync
Version: 2.6.7
Platform: x86
OS/Version: Linux
Status: NEW
Severity: normal
https://bugzilla.samba.org/show_bug.cgi?id=3186
--- Comment #2 from [EMAIL PROTECTED] 2005-11-22 23:41 MST ---
What version are you using? You have 2.6.7 selected in the bug report, but
that's still in development.
The copy-on-write optimization wasn't done until v2.6.1 (Apr 2004):
https://bugzilla.samba.org/show_bug.cgi?id=3186
--- Comment #3 from [EMAIL PROTECTED] 2005-11-23 00:34 MST ---
I'm actually using 2.6.7. In fact, I'm using a version from CVS in which Wayne
added --min-size and --max-size, and fixed (and then re-fixed) a bug in hlink.
This isn't
https://bugzilla.samba.org/show_bug.cgi?id=2607
--- Comment #7 from [EMAIL PROTECTED] 2005-11-23 14:09 MST ---
(In reply to comment #6)
The problem is that glibc's implementation (2.3.5) of strftime() calls tzset(),
which attempts to reload the timezone information. If the
https://bugzilla.samba.org/show_bug.cgi?id=3186
--- Comment #6 from [EMAIL PROTECTED] 2005-11-23 23:07 MST ---
I tried adding --delete-during (so the full invocation now looks like rsync
-vrltH --delete -pgo --stats -z -D --numeric-ids -i --delete-during
https://bugzilla.samba.org/show_bug.cgi?id=3186
--- Comment #7 from [EMAIL PROTECTED] 2005-11-24 11:27 MST ---
You are right that dervish does not need to use --delete when copying into a
new directory, but it also doesn't hurt anything (since it won't actually do
much of anything).
https://bugzilla.samba.org/show_bug.cgi?id=3186
--- Comment #8 from [EMAIL PROTECTED] 2005-11-24 12:28 MST ---
Yikes. Well, I'm certainly runnning 2.6 on everything here.
You're certainly in a better position than I am to try to bug-report this to
the kernel developers; is that
https://bugzilla.samba.org/show_bug.cgi?id=3271
--- Comment #3 from [EMAIL PROTECTED] 2005-11-24 19:30 MST ---
OK, further research has shown that I was not quite right about the cause of
the problem. In my tests, the network i/o process does die, and it's the
generator process that
https://bugzilla.samba.org/show_bug.cgi?id=3271
--- Comment #5 from [EMAIL PROTECTED] 2005-11-26 10:08 MST ---
Created an attachment (id=1594)
-- (https://bugzilla.samba.org/attachment.cgi?id=1594action=view)
patch to prevent lingering processes
This causes the writefd_unbuffered
https://bugzilla.samba.org/show_bug.cgi?id=3271
[EMAIL PROTECTED] changed:
What|Removed |Added
Attachment #1595 is|0 |1
obsolete|
https://bugzilla.samba.org/show_bug.cgi?id=3298
Summary: --rsh option incorrectly interprets quotes
Product: rsync
Version: 2.6.6
Platform: x86
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P3
https://bugzilla.samba.org/show_bug.cgi?id=3271
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |ASSIGNED
--- Comment #8 from
https://bugzilla.samba.org/show_bug.cgi?id=3277
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |ASSIGNED
--- Comment #1 from
https://bugzilla.samba.org/show_bug.cgi?id=3271
--- Comment #9 from [EMAIL PROTECTED] 2005-12-02 21:23 MST ---
(In reply to comment #8)
Thanks for the suggested patches. I agree that those continue statements
after
select() returns -1 look like they should be improved, but I'm
https://bugzilla.samba.org/show_bug.cgi?id=3271
[EMAIL PROTECTED] changed:
What|Removed |Added
Attachment #1604 is|0 |1
obsolete|
https://bugzilla.samba.org/show_bug.cgi?id=3299
Summary: rsync: now replaces non-ASCII character with numerical
values
Product: rsync
Version: 2.6.6
Platform: Other
URL:
https://bugzilla.samba.org/show_bug.cgi?id=3304
Summary: on --delay-updates remove .~tmp~ recursively
Product: rsync
Version: 2.6.6
Platform: x64
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P3
https://bugzilla.samba.org/show_bug.cgi?id=3305
Summary: -t copies always too many files to mounted windows
volume -c copies no files
Product: rsync
Version: 2.6.7
Platform: Other
OS/Version: Linux
Status: NEW
https://bugzilla.samba.org/show_bug.cgi?id=3305
--- Comment #1 from [EMAIL PROTECTED] 2005-12-07 05:10 MST ---
The comment about always copying 50% of the files to a mounted Windows
directory pretty much identifies the problem.
See the --modify-window option for the solution.
--
https://bugzilla.samba.org/show_bug.cgi?id=3277
[EMAIL PROTECTED] changed:
What|Removed |Added
CC||foner-rsync-
|
https://bugzilla.samba.org/show_bug.cgi?id=3305
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
https://bugzilla.samba.org/show_bug.cgi?id=3298
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
https://bugzilla.samba.org/show_bug.cgi?id=2802
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
https://bugzilla.samba.org/show_bug.cgi?id=3334
Summary: some time rsync is exiting with received SIGUSR1 or
SIGINT (code 20) at rsync.c(229).
Product: rsync
Version: 2.6.6
Platform: All
OS/Version: Linux
Status:
https://bugzilla.samba.org/show_bug.cgi?id=3175
[EMAIL PROTECTED] changed:
What|Removed |Added
Severity|normal |enhancement
https://bugzilla.samba.org/show_bug.cgi?id=3334
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
https://bugzilla.samba.org/show_bug.cgi?id=2947
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|
https://bugzilla.samba.org/show_bug.cgi?id=3358
Summary: rsync chokes on large files
Product: rsync
Version: 2.6.6
Platform: PPC
OS/Version: Mac OS X
Status: NEW
Severity: major
Priority: P3
Component:
https://bugzilla.samba.org/show_bug.cgi?id=3358
--- Comment #1 from [EMAIL PROTECTED] 2005-12-28 11:21 MST ---
The pertinent error is this:
rsync: write failed on /test: No space left on device (28)
That is an error from your OS that indicates that there was no room to write
out
https://bugzilla.samba.org/show_bug.cgi?id=3358
--- Comment #2 from [EMAIL PROTECTED] 2005-12-29 13:47 MST ---
Intereseting, didn't knwo that rsync worked that way - I thought the default
behaviour was to only replace the parts of the file that had changed. Anyway,
this motivates a
https://bugzilla.samba.org/show_bug.cgi?id=3358
--- Comment #3 from [EMAIL PROTECTED] 2005-12-29 13:48 MST ---
Btw, I am just trying your suggestions. First I will try the inplace switch and
secondly I will test syncing with twice the amount of space required for the
file available.
https://bugzilla.samba.org/show_bug.cgi?id=3358
--- Comment #4 from [EMAIL PROTECTED] 2005-12-29 13:54 MST ---
Sorry for spamming, but I just realised what you meant when you wrote:
You can use the --checksum option to avoid this unneeded update at the expense
of a lot of extra disk
https://bugzilla.samba.org/show_bug.cgi?id=3362
Summary: Add option to normalize Unicode filenames
Product: rsync
Version: 2.6.7
Platform: Other
OS/Version: All
Status: NEW
Severity: enhancement
Priority: P3
https://bugzilla.samba.org/show_bug.cgi?id=2938
[EMAIL PROTECTED] changed:
What|Removed |Added
CC||[EMAIL PROTECTED]
--- Comment
https://bugzilla.samba.org/show_bug.cgi?id=3363
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
https://bugzilla.samba.org/show_bug.cgi?id=3358
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
https://bugzilla.samba.org/show_bug.cgi?id=3358
--- Comment #6 from [EMAIL PROTECTED] 2006-01-02 10:21 MST ---
This is weird, there is no network activity during this building file list
phase. However, as soon as it is finished, rsync saturates my network.
I thought rsync worked, if
https://bugzilla.samba.org/show_bug.cgi?id=3358
--- Comment #7 from [EMAIL PROTECTED] 2006-01-02 11:02 MST ---
(In reply to comment #6)
This is weird, there is no network activity during this building file list
phase. However, as soon as it is finished, rsync saturates my network.
https://bugzilla.samba.org/show_bug.cgi?id=3358
--- Comment #8 from [EMAIL PROTECTED] 2006-01-02 11:42 MST ---
What is weird about that?
You wrote in a previous comment when I asked why rsync is considering a file
for 30 minutes if it is not checksumming it:
Because it is
https://bugzilla.samba.org/show_bug.cgi?id=3371
Summary: no way to limit disk IO bandwidth
Product: rsync
Version: 2.6.6
Platform: x86
URL: https://bugzilla.samba.org/show_bug.cgi?id=2800
OS/Version: Linux
Status: NEW
https://bugzilla.samba.org/show_bug.cgi?id=3382
--- Comment #1 from [EMAIL PROTECTED] 2006-01-06 14:46 MST ---
Created an attachment (id=1652)
-- (https://bugzilla.samba.org/attachment.cgi?id=1652action=view)
clearerr() before trying getc() again, otherwise may loop indefinitely
https://bugzilla.samba.org/show_bug.cgi?id=3382
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
https://bugzilla.samba.org/show_bug.cgi?id=3392
Summary: fuzzy misbehaving if source is a file
Product: rsync
Version: 2.6.6
Platform: All
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P3
https://bugzilla.samba.org/show_bug.cgi?id=3392
--- Comment #1 from [EMAIL PROTECTED] 2006-01-10 17:22 MST ---
This behavior is a consequence of the strange logic in get_local_name in
main.c. If the destination path is given as a file, then rsync uses a local
name and accesses the
https://bugzilla.samba.org/show_bug.cgi?id=3392
--- Comment #2 from [EMAIL PROTECTED] 2006-01-10 17:22 MST ---
Created an attachment (id=1661)
-- (https://bugzilla.samba.org/attachment.cgi?id=1661action=view)
main.c from my custom rsync, showing rewritten get_local_name
--
https://bugzilla.samba.org/show_bug.cgi?id=3392
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
https://bugzilla.samba.org/show_bug.cgi?id=3392
--- Comment #4 from [EMAIL PROTECTED] 2006-01-15 08:19 MST ---
Nice. It occurs to me that maybe the first call to do_stat should be changed
to link_stat(dest_path, st, keep_dirlinks) in order to obey --keep-dirlinks
when finding the
https://bugzilla.samba.org/show_bug.cgi?id=3304
[EMAIL PROTECTED] changed:
What|Removed |Added
CC||[EMAIL PROTECTED]
--- Comment
https://bugzilla.samba.org/show_bug.cgi?id=3415
Summary: -R and --delete cause --delete to be ignored
Product: rsync
Version: 2.6.6
Platform: Other
OS/Version: Windows 2000
Status: NEW
Severity: major
Priority: P3
https://bugzilla.samba.org/show_bug.cgi?id=2790
--- Comment #3 from [EMAIL PROTECTED] 2006-01-16 20:51 MST ---
I've been working on a filename-conversion solution that uses the iconv()
function. After putting a bunch of thought into various designs, I think I
have a good solution
https://bugzilla.samba.org/show_bug.cgi?id=3299
[EMAIL PROTECTED] changed:
What|Removed |Added
Severity|major |normal
Status|NEW
https://bugzilla.samba.org/show_bug.cgi?id=3415
--- Comment #1 from [EMAIL PROTECTED] 2006-01-17 12:20 MST ---
I can't duplicate this. Is the version of rsync that the daemon is running
old? Are the command-lines you cited modified at all from what failed?
--
Configure bugmail:
https://bugzilla.samba.org/show_bug.cgi?id=3304
--- Comment #3 from [EMAIL PROTECTED] 2006-01-17 14:01 MST ---
Perfectly understandable. As for now a hint in the in the manpage (or at
runtime, when 'stale' .~tmp~ directories are encountered) should suffice, since
the current
https://bugzilla.samba.org/show_bug.cgi?id=3304
--- Comment #4 from [EMAIL PROTECTED] 2006-01-17 14:56 MST ---
Perhaps the special treatment of the .~tmp~ directory could be implemented by
placing a receiving-end protect filter on any files inside it.
--
Configure bugmail:
https://bugzilla.samba.org/show_bug.cgi?id=3422
Summary: dry run fails when encountering dangling symbolic link
Product: rsync
Version: 2.6.4
Platform: All
OS/Version: Linux
Status: NEW
Severity: normal
Priority:
https://bugzilla.samba.org/show_bug.cgi?id=3415
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
https://bugzilla.samba.org/show_bug.cgi?id=3422
--- Comment #1 from [EMAIL PROTECTED] 2006-01-18 19:47 MST ---
I reproduced this bug with my custom rsync 2.6.6.matt.7. According to verbose
output, delete_in_dir(link) seems to be getting called erroneously on the
receiver. I'm
https://bugzilla.samba.org/show_bug.cgi?id=3422
--- Comment #2 from [EMAIL PROTECTED] 2006-01-18 20:38 MST ---
Created an attachment (id=1702)
-- (https://bugzilla.samba.org/attachment.cgi?id=1702action=view)
Makes receiving rsync process deletions only in directories
I found the
https://bugzilla.samba.org/show_bug.cgi?id=3422
--- Comment #3 from [EMAIL PROTECTED] 2006-01-19 00:46 MST ---
(In reply to comment #2)
This sounds like a good solution. Thanks, I didn't expect a response so
quickly! Shall I test this out with the latest rsync?
You already did some
https://bugzilla.samba.org/show_bug.cgi?id=3422
--- Comment #4 from [EMAIL PROTECTED] 2006-01-19 06:57 MST ---
Yes, please do take a recent source RPM or source tarball and try the patch.
If you use rpmbuild, you can get it to apply the patch automatically after
unpacking the source
https://bugzilla.samba.org/show_bug.cgi?id=3422
--- Comment #5 from [EMAIL PROTECTED] 2006-01-19 07:46 MST ---
(In reply to comment #4)
OK, I will do that (have done rpm's before), but it will take some time, as I'm
rather busy at the moment (~2 weeks). This way, Wayne also has some
https://bugzilla.samba.org/show_bug.cgi?id=3304
--- Comment #5 from [EMAIL PROTECTED] 2006-01-19 13:15 MST ---
Surprise: according to the man page of 2.6.6, a receiving-end protect filter is
indeed placed on the partial dir, which is the same as the delay-updates dir.
Never mind
https://bugzilla.samba.org/show_bug.cgi?id=3430
Summary: Error with ACL-patch and -x on mountpoint
Product: rsync
Version: 2.6.6
Platform: Other
OS/Version: FreeBSD
Status: NEW
Severity: minor
Priority: P3
https://bugzilla.samba.org/show_bug.cgi?id=3430
--- Comment #1 from [EMAIL PROTECTED] 2006-01-20 10:06 MST ---
The issue is that, when rsync detects that a directory is on another
filesystem, it sends the directory itself but skips the contents. See
send_directory in flist.c: it
https://bugzilla.samba.org/show_bug.cgi?id=3430
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |ASSIGNED
--- Comment #2 from
https://bugzilla.samba.org/show_bug.cgi?id=3362
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
https://bugzilla.samba.org/show_bug.cgi?id=2790
[EMAIL PROTECTED] changed:
What|Removed |Added
CC||[EMAIL PROTECTED]
--- Comment
https://bugzilla.samba.org/show_bug.cgi?id=3430
--- Comment #3 from [EMAIL PROTECTED] 2006-01-20 11:57 MST ---
(In reply to comment #2)
No, we copy the mount-point directory on purpose because we want it to be
there
should the remote system need to mount their own filesystem at
https://bugzilla.samba.org/show_bug.cgi?id=3430
--- Comment #4 from [EMAIL PROTECTED] 2006-01-20 13:02 MST ---
I know of no way to find the attributes of the underlying mount-point directory
when the mount is present. And leaving out the mount-point dir is not an
improvement in my
https://bugzilla.samba.org/show_bug.cgi?id=3430
--- Comment #5 from [EMAIL PROTECTED] 2006-01-20 13:43 MST ---
(In reply to comment #4)
We could make this user-selectable by letting the user repeat the -x option to
choose to eliminate the mount-point dirs from the transfer.
In
https://bugzilla.samba.org/show_bug.cgi?id=3430
--- Comment #6 from [EMAIL PROTECTED] 2006-01-20 15:03 MST ---
Created an attachment (id=1704)
-- (https://bugzilla.samba.org/attachment.cgi?id=1704action=view)
Makes -x -x exclude mount points themselves
This patch should do it.
https://bugzilla.samba.org/show_bug.cgi?id=3430
--- Comment #7 from [EMAIL PROTECTED] 2006-01-21 09:16 MST ---
AFAIK, other tools that have a don't-traverse-file-systems option (find, du,
..) in the unix world ignore the mount point (as it logically belongs to the
fs you don't want
https://bugzilla.samba.org/show_bug.cgi?id=3430
--- Comment #8 from [EMAIL PROTECTED] 2006-01-21 13:35 MST ---
Created an attachment (id=1705)
-- (https://bugzilla.samba.org/attachment.cgi?id=1705action=view)
Suggested changes to man page for --one-file-system
Wayne seems to have
https://bugzilla.samba.org/show_bug.cgi?id=3432
Summary: rsync -azv --cvs-exclude forgets LocalSettings.php
Product: rsync
Version: 2.6.6
Platform: x86
URL: http://pto.linux.dk/albackup.tgz
OS/Version: Linux
Status: NEW
https://bugzilla.samba.org/show_bug.cgi?id=3432
--- Comment #1 from [EMAIL PROTECTED] 2006-01-21 14:26 MST ---
--cvs-ignore ignores both that laundry list in exclude.c and any additional
files specified in per-directory .cvsignore files. I downloaded the package
you linked and found
https://bugzilla.samba.org/show_bug.cgi?id=3432
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
https://bugzilla.samba.org/show_bug.cgi?id=3444
Summary: Cygwin files trashed when they only differ in the case
of the name
Product: rsync
Version: 2.6.6
Platform: x86
OS/Version: Windows XP
Status: NEW
https://bugzilla.samba.org/show_bug.cgi?id=3444
--- Comment #1 from [EMAIL PROTECTED] 2006-01-25 16:38 MST ---
It's pretty clear that the trouble is the case insensitivity of the filesystem.
In fact, I reproduced this behavior on a vfat partition mounted on Linux:
mkdir test1
https://bugzilla.samba.org/show_bug.cgi?id=3461
Summary: rsync is not atomic when temp-dir is on different device
Product: rsync
Version: 2.6.7
Platform: Other
OS/Version: Linux
Status: NEW
Severity: enhancement
https://bugzilla.samba.org/show_bug.cgi?id=3461
--- Comment #1 from [EMAIL PROTECTED] 2006-01-28 14:19 MST ---
I don't see how using a --temp-dir on a different device could make the
transfer faster, if indeed it does. At some point, all of the data of file.dat
must go from memory
https://bugzilla.samba.org/show_bug.cgi?id=3461
--- Comment #2 from [EMAIL PROTECTED] 2006-01-28 16:45 MST ---
I was a bit unclear, it's not that it's just a different device, it's a
different physical disk.
For a dataset of about 45GB we see an rsync time of about 2 hrs. When we
https://bugzilla.samba.org/show_bug.cgi?id=3461
--- Comment #3 from [EMAIL PROTECTED] 2006-01-28 18:27 MST ---
Hmmm. It's true that rsync interleaves memory-mapped reads from the basis file
and writes to the temporary file. A smart disk scheduler should avoid making
the head dart
https://bugzilla.samba.org/show_bug.cgi?id=3444
[EMAIL PROTECTED] changed:
What|Removed |Added
Severity|critical|enhancement
Status|NEW
https://bugzilla.samba.org/show_bug.cgi?id=2868
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|
https://bugzilla.samba.org/show_bug.cgi?id=3277
[EMAIL PROTECTED] changed:
What|Removed |Added
Severity|normal |enhancement
https://bugzilla.samba.org/show_bug.cgi?id=3430
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|
https://bugzilla.samba.org/show_bug.cgi?id=2240
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|
https://bugzilla.samba.org/show_bug.cgi?id=3461
--- Comment #5 from [EMAIL PROTECTED] 2006-01-29 02:04 MST ---
Created an attachment (id=1712)
-- (https://bugzilla.samba.org/attachment.cgi?id=1712action=view)
Make the --partial-dir get used when copying
As mentioned, if --temp-dir
https://bugzilla.samba.org/show_bug.cgi?id=3461
--- Comment #6 from [EMAIL PROTECTED] 2006-01-29 03:30 MST ---
The traditional use of --temp-dir (I think) is for situations when the
receiving partition does not have enough free space to accomodate a temporary
copy of a large file.
https://bugzilla.samba.org/show_bug.cgi?id=3277
[EMAIL PROTECTED] changed:
What|Removed |Added
CC||[EMAIL PROTECTED]
--- Comment
https://bugzilla.samba.org/show_bug.cgi?id=3461
--- Comment #7 from [EMAIL PROTECTED] 2006-01-29 14:17 MST ---
(In reply to comment #6)
The traditional use of --temp-dir (I think) is for situations when the
receiving partition does not have enough free space to accomodate a
https://bugzilla.samba.org/show_bug.cgi?id=3277
--- Comment #6 from [EMAIL PROTECTED] 2006-01-30 11:56 MST ---
(In reply to comment #5)
In fact, would anyone object if the non-root meaning of -a changed
to behavior #3?
Yes -- I would. I do a lot of copying where I want the
https://bugzilla.samba.org/show_bug.cgi?id=3277
--- Comment #7 from [EMAIL PROTECTED] 2006-01-30 14:36 MST ---
(In reply to comment #6)
Yes -- I would. I do a lot of copying where I want the permissions and groups
copied exactly from the source.
If you care about the permissions
https://bugzilla.samba.org/show_bug.cgi?id=3277
--- Comment #8 from [EMAIL PROTECTED] 2006-01-30 15:12 MST ---
This is not really the place to hold a tangent conversatation, but no, I don't
want behavior #2, as I'm not running as root (but I do have multiple groups
associated with my
https://bugzilla.samba.org/show_bug.cgi?id=3465
Summary: --files-from does not --delete
Product: rsync
Version: 2.6.6
Platform: Other
OS/Version: AIX
Status: NEW
Severity: normal
Priority: P3
Component:
1 - 100 of 133 matches
Mail list logo
