I'm not really blaming the user. If it were up to me, -v would include -i.
On 2/9/24 05:36, Andreas Gruenbacher wrote:
On Sun, Feb 4, 2024 at 7:20 PM Kevin Korb via rsync
wrote:
rsync's -v is fairly useless. Learn to use -i instead or in addition to.
Well, note that I didn't say anything a
On Sun, Feb 4, 2024 at 7:20 PM Kevin Korb via rsync
wrote:
> rsync's -v is fairly useless. Learn to use -i instead or in addition to.
Well, note that I didn't say anything about the lib/ directory in that
command; it's just that rsync decided to remove the symlink component
from the path lib/mod
rsync's -v is fairly useless. Learn to use -i instead or in addition to.
On 2/4/24 12:58, Andreas Gruenbacher via rsync wrote:
Hello,
when trying to rsync files between hosts, I ran into a surprising case
in which rsync replaces a symlink with a directory, with no indication
of any kind.
In t
Hello,
when trying to rsync files between hosts, I ran into a surprising case
in which rsync replaces a symlink with a directory, with no indication
of any kind.
In the following reproducer, rsync is called as follows:
rsync --verbose --recursive --relative --delete a/./lib/modules b/
Directo
ecifically requested that dvi files not be transferred. I choose that
myself in a regular configuration file. So shouldn't it be a WARNING rather
than an ERROR? I would expect to see
In this case you're in control of both ends of the transfer, so you know
that *.dvi files won't
gt; ...
>
> I understand that the remote daemon has refused file demo.dvi because I
> specifically requested that dvi files not be transferred. I choose that
> myself in a regular configuration file. So shouldn't it be a WARNING rather
> than an ERROR? I would expect to se
transferred. I choose that myself
in a regular configuration file. So shouldn't it be a WARNING rather than an
ERROR? I would expect to see
WARNING: daemon refused to receive file "rprice/demo.dvi"
Roger
--
Please use reply-all for most replies to avoid omitting the mailing
On Thu, Sep 17, 2020 at 5:32 AM Matt McCutchen wrote:
> For the "not transfer" part, I can use --ignore-existing, but I don't see
> a direct way to be warned only about source files that differ from
> existing destination files.
>
Indeed, the 2-step approach that you mentioned is all that the rel
hat exist on the destination, whether or not they
differ. So as a workaround, after the --ignore-existing run, I'm using
a separate dry run without --ignore-existing to warn about any
remaining differences.
Is there a better solution? Do people think that filing an enhancement
request to show
g the
> hashing to return bogus results.
>
> On 6/3/19 6:09 AM, sambalist--- via rsync wrote:
>> Hi there!
>>
>> On a daily backup script, I am getting a lot of these messages:
>>
>> WARNING: -- update retained (will try again).
>>
>> I've t
of these messages:
>
> WARNING: -- update retained (will try again).
>
> I've tried googling, but i can't figure out what these messages exactly
> mean and how i can solve them.
>
>
Hi there!
On a daily backup script, I am getting a lot of these messages:
WARNING: -- update retained (will try again).
I've tried googling, but i can't figure out what these messages exactly
mean and how i can solve them.
Any hint?
Thank you
Gabriele
--
GPG Key Fingerprint:
suddenly gets a warning every time he
tries to copy?
--
You are receiving this mail because:
You are the QA Contact for the bug.
--
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
https://bugzilla.samba.org/show_bug.cgi?id=13222
Wayne Davison changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://bugzilla.samba.org/show_bug.cgi?id=13222
--- Comment #1 from Urban Mueller ---
in the short description, I meant to say "chmod" not "chown", sorry.
--
You are receiving this mail because:
You are the QA Contact for the bug.
--
Please use reply-all for most replies to avoid omitting th
https://bugzilla.samba.org/show_bug.cgi?id=13222
Bug ID: 13222
Summary: rsync creates warning if time of destination file
differs in fractional part of second and owner
mismatches
Product: rsync
Version: 3.1.2
mes and decide if it is a problem or not.
>
> On 09/07/2017 10:27 AM, Vangelis Katsikaros via rsync wrote:
>> Hi
>>
>> I would like to ask, when the "vanished files" warning is a sign that
>> something bad is happening somewhere. I know that the `rsync-no-
"vanished files" warning is a sign that
> something bad is happening somewhere. I know that the `rsync-no-vanished`
> script can silence the warning, but I am wondering whether this is a sane
> thing to do.
>
> My guess based on https://bugzilla.samba.org/sho
Hi
I would like to ask, when the "vanished files" warning is a sign that something
bad is happening somewhere. I know that the `rsync-no-vanished` script can
silence the warning, but I am wondering whether this is a sane thing to do.
My guess based on https://bugzilla.samba.org/show_
course I didn't notice that groups
hadn't been backed up, which in turns broke the server.
I had a similar issue with --chmod, which must be used with --perms or else
it's also silently ignored, and there are probably other cases.
I think it would be more user-friendly to display a warni
https://bugzilla.samba.org/show_bug.cgi?id=3653
--- Comment #27 from samba ---
Still an issue on rsync-3.1.1-3 as found on Debian 8
--
You are receiving this mail because:
You are the QA Contact for the bug.
--
Please use reply-all for most replies to avoid omitting the mailing list.
To unsub
https://bugzilla.samba.org/show_bug.cgi?id=10989
--- Comment #2 from Jim Avera ---
A much more serious problem is that when "unsafe" symlinks are copied pursuant
to the --copy-unsafe-links option, they are all treated as I/O ERRORS.
This prevents --delete from ever working.
--
You are receivin
https://bugzilla.samba.org/show_bug.cgi?id=10989
--- Comment #1 from Jim Avera ---
Created attachment 10497
--> https://bugzilla.samba.org/attachment.cgi?id=10497&action=edit
Demo script
--
You are receiving this mail because:
You are the QA Contact for the bug.
--
Please use reply-all for m
https://bugzilla.samba.org/show_bug.cgi?id=10989
Bug ID: 10989
Summary: "copying unsafe symlink" warning should not occur if
file is not changing
Product: rsync
Version: 3.1.1
Hardware: All
https://bugzilla.samba.org/show_bug.cgi?id=3653
Wayne Davison changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
https://bugzilla.samba.org/show_bug.cgi?id=3653
--- Comment #25 from jakob...@gmail.com 2014-01-01 15:04:58 UTC ---
What remains to be done is to make the the rsync-no-vanished script accessible
to users. I created bug 10356 about including it in the tarball.
--
Configure bugmail: https://bugzil
https://bugzilla.samba.org/show_bug.cgi?id=3653
Nick Hibma changed:
What|Removed |Added
CC||n...@anywi.com
--- Comment #24 from Nick Hibma
https://bugzilla.samba.org/show_bug.cgi?id=8895
Toralf Förster changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
https://bugzilla.samba.org/show_bug.cgi?id=8895
Kevin Korb changed:
What|Removed |Added
CC|rs...@sanitarium.net|
--- Comment #3 from Kevin Korb 2012-04-25 19
https://bugzilla.samba.org/show_bug.cgi?id=8895
--- Comment #2 from Toralf Förster 2012-04-25 19:32:03
UTC ---
Ah - thx, therefore not a bug (but then I must mis the line with the vanished
file name ...)
BTW do you know, whether a special return code is used in this case ? Then I
could catch th
Kevin Korb 2012-04-25 19:09:21 UTC
---
This warning happens whenever rsync sees a file during the indexing phase but
by the time it gets around to actually copying the file it is no longer there
(as in something else deleted it).
This is most common on things like email spools but I can see a compile
https://bugzilla.samba.org/show_bug.cgi?id=8895
Summary: rsync warning: some files vanished
Product: rsync
Version: 3.0.9
Platform: x86
OS/Version: Linux
Status: NEW
Severity: major
Priority: P5
Component
IO error encountered -- skipping file deletion
sent 7900103 bytes received 31665465290 bytes 1978039.99 bytes/sec
total size is 281386128794 speedup is 8.88
rsync warning: some files vanished before they could be transferred (code 24)
at main.c(1508) [generator=3.0.7]
--
Conf
https://bugzilla.samba.org/show_bug.cgi?id=3653
--- Comment #22 from g...@delfi.ee 2011-01-25 13:55 CST ---
Created an attachment (id=6228)
--> (https://bugzilla.samba.org/attachment.cgi?id=6228&action=view)
updated patch in #c1 against rsync-3.0.7
--
Configure bugmail: https://bu
https://bugzilla.samba.org/show_bug.cgi?id=3653
--- Comment #21 from m...@mattmccutchen.net 2010-11-21 21:12 CST ---
(In reply to comment #20)
> AFAICS, delete_in_dir() suppresses deletion when /any/ flag is set in
> io_error:
>
> if (io_error && !ignore_errors) {
Indeed, t
https://bugzilla.samba.org/show_bug.cgi?id=3653
--- Comment #20 from jr-sambabugzi...@quo.to 2010-11-21 19:43 CST ---
(In reply to comment #19)
> You're right that the IOERR_GENERAL flag (which corresponds to that message)
> stops all destination files from being deleted. But it is o
https://bugzilla.samba.org/show_bug.cgi?id=3653
--- Comment #19 from m...@mattmccutchen.net 2010-11-21 17:57 CST ---
(In reply to comment #18)
> What's also annoying is that a "vanished file" warning triggers:
>
> "IO error encountered -- skipping fil
--- Comment #18 from jr-sambabugzi...@quo.to 2010-11-20 12:47 CST ---
+1 for --ignore-vanished. Filtering out the warnings when stdout and stderr are
redirected to different places isn't so trivial.
What's also annoying is that a "vanished file" warning triggers:
&
ackup : http://www.lbackup.org
Just one rsync based backup possibility.
Note : The current version 0.9.8r5-alpha3 of LBackup, requires a wrapper script
to be
put around rsync if you want to ignore the vanished files warning. :
http://www.lbackup.org/developer/ignore_vanished_file_warnings
A
https://bugzilla.samba.org/show_bug.cgi?id=3653
j...@jwz.org changed:
What|Removed |Added
CC||j...@jwz.org
--- Comment #17 from j..
Here is the mail from henri.
Best regards,
Vitorio
Début du message réexpédié :
De : henri
Date : 4 juin 2009 00:30:32 HAEC
À : Mac User FR
Objet : Rép : WARNING: . . . .failed verification -- update
discarded (will try again).
I was going to write a daemon to manage suspend and resume
On Thursday 04 June 2009 10:28:00 you wrote:
> JW (j...@mailsw.com) wrote on 3 June 2009 11:58:
> >A nightly scripted rsync backup job is giving me this error
> >
> >WARNING: vm/escDebLenny14G-flat.vmdk failed verification -- update
> > discarded (will try again).
JW (j...@mailsw.com) wrote on 3 June 2009 11:58:
>A nightly scripted rsync backup job is giving me this error
>
>WARNING: vm/escDebLenny14G-flat.vmdk failed verification -- update discarded
>(will try again).
>
>I've searched the web and I think probably the pro
:
A nightly scripted rsync backup job is giving me this error
WARNING: vm/escDebLenny14G-flat.vmdk failed verification -- update
discarded
(will try again).
I've searched the web and I think probably the problem is the source
file
changed during the copy.
However, I haven't seen any e
You can't copy the disk image of a vm while the guest OS is running.
Best regards,
Vitorio
Le 3 juin 09 à 18:58, JW a écrit :
A nightly scripted rsync backup job is giving me this error
WARNING: vm/escDebLenny14G-flat.vmdk failed verification -- update
discarded
(will try again).
A nightly scripted rsync backup job is giving me this error
WARNING: vm/escDebLenny14G-flat.vmdk failed verification -- update discarded
(will try again).
I've searched the web and I think probably the problem is the source file
changed during the copy.
However, I haven'
from r...@golder.org 2009-05-18 07:59 CST ---
This is a 'me too' for '--ignore-vanished-files' flag. Lots of legitimate cases
where files could vanish, so having the option to treat this as normal (i.e.
prevent rsync from producing this warning and ensure a zero exit val
https://bugzilla.samba.org/show_bug.cgi?id=3653
--- Comment #15 from o...@yadan.net 2009-04-22 03:51 CST ---
I ended up using the following script for snapback2 (which exits with the same
error codes as rsync if rsync fails:
# cat /etc/cron.daily/snapback2
#! /bin/sh
OUT=`/usr/bin/sn
https://bugzilla.samba.org/show_bug.cgi?id=3653
--- Comment #14 from rv-rsyncbugzi...@eychenne.org 2009-04-22 03:39 CST
---
I also find this warning annoying, I really vote for this patch.
--
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
--- You are
Hi all,
The part about the -S option in the rsync man page says:
-S, --sparse
Try to handle sparse files efficiently so they take up
less space on the destination. Conflicts with
--inplace because it's not possible to overwrite data
in a spars
#13 from [EMAIL PROTECTED] 2008-07-14 16:24 CST ---
Guys, I also find this warning annoying.
I get a pretty much daily email about it from my backup 'failing'.
/etc/cron.daily/snapback2:
rsync warning: some files vanished before they could be transferred (code 24)
at main.c(1515)
On Tue, Dec 18, 2007 at 06:31:06PM -0800, [EMAIL PROTECTED] wrote:
> Any concerns with the compiler warning on flist.c on a ia64 system
> running SLES10SP1?
Unfortunately the warning was on the assembler file produced, so I don't
know if that means anything should be improved in the f
Any concerns with the compiler warning on flist.c on a ia64 system
running SLES10SP1?
~/rsync-3.0.0pre7> make
gcc -std=gnu99 -g -O2 -DHAVE_CONFIG_H -Wall -W -o mkrounding -I. ./
mkrounding.c
./mkrounding >rounding.h
Rounding file_extras in multiples of 2 (EXTRA_LEN=4, FILE_STRUCT_
unding >rounding.h
Rounding file_extras in multiples of 2 (EXTRA_LEN=4, FILE_STRUCT_LEN=24)
gcc -std=gnu99 -I. -I. -g -O2 -DHAVE_CONFIG_H -Wall -W -I./popt -c
flist.c -o flist.o
/tmp/ccC7MQuD.s: Assembler messages:
/tmp/ccC7MQuD.s:2993: Warning: Use of 'mov' may violate WAW
dependency
unding >rounding.h
Rounding file_extras in multiples of 2 (EXTRA_LEN=4, FILE_STRUCT_LEN=24)
gcc -std=gnu99 -I. -I. -g -O2 -DHAVE_CONFIG_H -Wall -W -I./popt -c
flist.c -o flist.o
/tmp/ccC7MQuD.s: Assembler messages:
/tmp/ccC7MQuD.s:2993: Warning: Use of 'mov' may violate WAW
dependency
On 7/20/07, Abdul Khan <[EMAIL PROTECTED]> wrote:
What does this line mean? Its been there in the summary every time i run
the rsync command.
rsync warning: some files vanished before they could be transferred
(code 24) at main.c(977) [sender=2.6.9]
Can anybody please shed the light abo
Hi folks,
What does this line mean? Its been there in the summary every time i run
the rsync command.
rsync warning: some files vanished before they could be transferred
(code 24) at main.c(977) [sender=2.6.9]
Can anybody please shed the light about the error code?
Thanks in advance
ak
I got a compiler warning on line 562 of receiver.c when I compiled
rsync with ACLs from CVS. The compiler did not like the assignment of
file->dirname (a const char *) to dn (a char *). The attached
metapatch to acls.diff fixes the warning and updates some line
numbers.
Matt
### Ecli
Our automatic virus detection agent has intercepted an email purporting to
have been sent from you:-
To: [EMAIL PROTECTED]
Subject:
Date: Fri May 12 13:06:35 2006
This email has NOT been delivered to the recipient.
Your computer may be infected with a virus, and this should be checked
an
https://bugzilla.samba.org/show_bug.cgi?id=3740
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|
https://bugzilla.samba.org/show_bug.cgi?id=3740
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|FIXED
https://bugzilla.samba.org/show_bug.cgi?id=3740
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|
https://bugzilla.samba.org/show_bug.cgi?id=3740
--- Comment #2 from [EMAIL PROTECTED] 2006-04-28 15:11 MST ---
One sample command from script is:
rsync --size-only -a -z --partial -L --delete \
--exclude-from=excludefile \
$srcHostDir \
$destDir
The emailed output from t
https://bugzilla.samba.org/show_bug.cgi?id=3740
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |ASSIGNED
--- Comment #1 from [EM
https://bugzilla.samba.org/show_bug.cgi?id=3740
Summary: --delete with -a failes with warning (though -a is
supposed to imply -r)
Product: rsync
Version: 2.6.8
Platform: x86
OS/Version: Linux
Status: NEW
https://bugzilla.samba.org/show_bug.cgi?id=3277
--- Comment #9 from [EMAIL PROTECTED] 2006-01-30 16:31 MST ---
I'm sorry for abusing your Bugzilla. Let the discussion continue on the
mailing list if necessary. Never mind changing the behavior of -a, but an
official alias for -rltE -
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=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 #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 perm
https://bugzilla.samba.org/show_bug.cgi?id=3277
[EMAIL PROTECTED] changed:
What|Removed |Added
CC||[EMAIL PROTECTED]
--- Comment #5
https://bugzilla.samba.org/show_bug.cgi?id=3277
[EMAIL PROTECTED] changed:
What|Removed |Added
Severity|normal |enhancement
Status|ASSIGNED
BTW, my test case is a sending rsync version 2.6.4-3 (Fedora FC4) and a
receiving rsync 2.6.3-1 (Fedora FC3).
Within a range of 25 or so minutes of --checksum-seed values (unix time
stamps), I see the warning for 3 times.
-Joe
Joe Peterson wrote:
> Wayne,
>
> I just did
Wayne,
I just did some more testing to see if I could reproduce the warning,
and I was successful. I tried manually setting "--checksum-seed" equal
to timestamps around the time of the error, and I hit a case pretty
quickly on that same file. It reproduces over and over, so it's
e, I think rsync should take all options
seriously (i.e. -ogD) whether or not it is root. I also think it should issue
a warning about every failure (i.e. every file) because all three of these
options can succeed on some files and fail on others and it's important that
the user gets the mes
conceptually simpler to me
than the peculiar other ways of specifying owner/group you mention below--and
extensible to other cases where the user may want to know that rsync wasn't
quite able to fulfill the request (e.g., ACL's or timestamps maybe).
I'm not sure whether it should complai
:) Yeah, I noticed that too! A little too coincidental for comfort!
Mike Daws wrote:
> On Wed, 2005-12-07 at 13:50 -0500, Chris Shoemaker wrote:
>
>>On Wed, Dec 07, 2005 at 11:38:25AM -0700, Joe Peterson wrote:
>>
>>>WARNING: jukebox/Frank_Sinatra/The_Main_Eve
On Wed, 2005-12-07 at 13:50 -0500, Chris Shoemaker wrote:
> On Wed, Dec 07, 2005 at 11:38:25AM -0700, Joe Peterson wrote:
> > WARNING: jukebox/Frank_Sinatra/The_Main_Event/04-Let_Me_Try_Again.flac
> > failed verification -- update discarded (will try again).
> >
> > Wh
good. The ethernet connection,
unless, as you say, there were a driver issue, should be TCP protected
(I am not specifying "-e", but it appears rsync chooses ssh as the
method by default).
I suppose I could have tripped upon an very obscure bug, but that's
probably unlikely (and yet
On Wed, Dec 07, 2005 at 11:38:25AM -0700, Joe Peterson wrote:
> WARNING: jukebox/Frank_Sinatra/The_Main_Event/04-Let_Me_Try_Again.flac
> failed verification -- update discarded (will try again).
> jukebox/Frank_Sinatra/The_Main_Event/12-My_Way.flac
>
> What does the "WA
Hey, I always have my gamma-ray shield with me! :)
But seriously, are you saying this indicates a read or write error?
I've googled for other cases of this, and when there was an error (like
an error reading a mounted partition), the error was reported before the
warning. In my case, no
On Wed, Dec 07, 2005 at 11:38:25AM -0700, Joe Peterson wrote:
> WARNING: jukebox/Frank_Sinatra/The_Main_Event/04-Let_Me_Try_Again.flac
> failed verification -- update discarded (will try again).
>
> What does the "WARNING" imply? What could have gone wrong? I cannot
>
oy_Brown.flac
jukebox/Frank_Sinatra/The_Main_Event/08-Angel_Eyes.flac
jukebox/Frank_Sinatra/The_Main_Event/09-You_Are_The_Sunshine_Of_My_Life.flac
jukebox/Frank_Sinatra/The_Main_Event/10-The_House_I_Live_In.flac
jukebox/Frank_Sinatra/The_Main_Event/11-My_Kind_Of_Town.flac
WARNING: juke
https://bugzilla.samba.org/show_bug.cgi?id=3277
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |ASSIGNED
--- Comment #1 from [EM
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
RSYNC ?
Presumably the system being shut down will kill off all processes, and
the remote rsync will die with some kind of a failed-connection error.
Is there any option to pop up the WARNING to the user, indicating the
Synchronization process ?
There's no
c will die with some kind of a failed-connection error.
> Is there any option to pop up the WARNING to the user, indicating the
> Synchronization process ?
There's nothing that can alert the user about a pending shutdown without
being logged into the server with a tty (in which case
Dear Wayne Davison,
What will happen if Node A / Node B is removed(shutdown/reboot)
when the Synchronization in progress through RSYNC ?
Is there any option to pop up the WARNING to the user, indicating the
Synchronization process ?
Please reply.
thanks & regards,
Lakshminaray
Content violation found in email message.
From: rsync@lists.samba.org
To: [EMAIL PROTECTED]
File(s): message.cmd
Matching filename: *.cmd
--
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.htm
Content violation found in email message.
From: rsync@lists.samba.org
To: [EMAIL PROTECTED]
Subject: Returned mail: Data format error
Matching Subject: returned mail: data format error
--
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: ht
https://bugzilla.samba.org/show_bug.cgi?id=1793
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|
https://bugzilla.samba.org/show_bug.cgi?id=1793
--- Additional Comments From [EMAIL PROTECTED] 2004-09-17 20:21 ---
Rawhide glibc had a bug that prevented a lot of packages from compiling.
Download the newer glibc (I'm using glibc-2.3.3-53) and things'll compile
again.
--
Config
https://bugzilla.samba.org/show_bug.cgi?id=1793
--- Additional Comments From [EMAIL PROTECTED] 2004-09-17 17:07 ---
Attached are the files you suggested that I take a look at.
Hope this helps.
I've got a working rsync that I got from a .rpm. So, I think it can work. hmmm
mybe the .
https://bugzilla.samba.org/show_bug.cgi?id=1793
--- Additional Comments From [EMAIL PROTECTED] 2004-09-17 17:02 ---
Created an attachment (id=669)
--> (https://bugzilla.samba.org/attachment.cgi?id=669&action=view)
glob.h for fedora rawhide
--
Configure bugmail: https://bugzilla.sa
https://bugzilla.samba.org/show_bug.cgi?id=1793
--- Additional Comments From [EMAIL PROTECTED] 2004-09-17 17:00 ---
Created an attachment (id=668)
--> (https://bugzilla.samba.org/attachment.cgi?id=668&action=view)
glob man page for fedora rawhide
--
Configure bugmail: https://bugz
https://bugzilla.samba.org/show_bug.cgi?id=1793
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |ASSIGNED
--- Additional Comments
https://bugzilla.samba.org/show_bug.cgi?id=1793
Summary: configure: WARNING: glob.h: present but cannot be
compiled
Product: rsync
Version: 2.6.3
Platform: All
OS/Version: Linux
Status: NEW
Severity
-- Virus Warning Message (on the network)
Found virus WORM_BAGLE.J in file TextFile.pif
The file TextFile.pif is moved to /var/spool/quarantine/virTCPZYry.U.
This is a machine-generated message, please do not reply via email. If you have
questions, please contact the Lucent
Warning - a possible virus was detected in your message to:
[EMAIL PROTECTED]
--
To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
> perl.htm
>> failed to set permissions on . : Operation not permitted
>> wrote 7426 bytes read 238 bytes 1021.87 bytes/sec
>> total size is 4728911 speedup is 617.03
>> rsync error: some files could not be transferred (code 23) at main.c(620)
>>
>> It would
t permitted
> wrote 7426 bytes read 238 bytes 1021.87 bytes/sec
> total size is 4728911 speedup is 617.03
> rsync error: some files could not be transferred (code 23) at main.c(620)
>
> It would be MUCH better if the warning would indicate where the error was
> LOCAL or REMOTE a
1 - 100 of 137 matches
Mail list logo
