If the model works thats fine but people who don't want to be on the
mailing list it's a nice way to look things up. I don't want to add
more complexity by adding bug tracking if what people are using today
is fine with them.
I think where we are at; is that we are just waiting for a volunteer
On Thu, Dec 05, 2002 at 03:39:18PM -0800, jw schultz wrote:
> Just to look at what it might look like i extracted the BUGS
> from NEWS and OLDNEWS to try formulating a list. The
> biggest problem with it is that the bugs are described
> according to the fix instead of the symptoms. I've attached
On Thu, Dec 05, 2002 at 01:38:25PM -0800, Sriram Ramkrishna wrote:
> What we do in the GNOME project is to find volunteers to run triage
> and catalog the bugs. If you have a "bugmaster" position who could
> coordinate something like this.
>
> Typically, if you have a bug system it's a good way
I came up with a patch to fix the problem of IO Errors caused by
excluded files as did Eugene V. Chupriyanov below.
Is there a chance that this change will show up in a future version of
rsync?
Is there a reason that we should not ignore IO errors when copy_links is
off? Just want to make su
Dave Dykstra wrote
> What about Linux? There's an O_DIRECT but the comment in asm/fcntl.h says
> it is currently ignored.
2.4.18, at least, honors O_DIRECT in generic_file_{read,write} via mm/filemap.c
-justinb
--
To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync
Thanks!
In other words, it would be using --blocking-io anyway, and I want it too
use --blocking-io, so the worst the --blocking-io option would be is
redundant if the *SERVER* box was compiled with RSYNC_RSH=rsh (which, in my
case, it wasn't). The --blocking-io option can't hurt and would be t
What we do in the GNOME project is to find volunteers to run triage
and catalog the bugs. If you have a "bugmaster" position who could
coordinate something like this.
Typically, if you have a bug system it's a good way to get more
contributers who want to start off small by fixing some of the s
First, as a newbie you should be aware that a lot of people think they
need to use daemon mode when they can do fine with the much simpler normal
rsh or ssh mode, so make sure you really do need it. Second, if you do
need it, make sure you can do 'telnet servername 873' and get a response,
otherwi
Dave,
Yes the problem was in the perl code. Chris was using my File::Rsync
perl module. He and 2 others reported a case where the module would
hang, but calling same rsync command from a shell would work properly.
I could not reproduce the symptom, but added some additional EOF checks
o
Well, i think i got the problem solved... Well, *I* didn't so much.
The problem was with the File::Rsync module itself that i was using (i guess
i didn't even mention that..?)
I got in contact with the author of the module and he said there was someone
just a week or so ago that emailed him hav
On Wed, Dec 04, 2002 at 04:42:35PM -0800, Sriram Ramkrishna wrote:
> Have you considered using bugzilla for reporting bugs? Just curious.
> I was looking on the rsync website and didn't see much in bug
> reporting.
There used to be another bug reporting system but it was being ignored
so Martin
On Wed, Dec 04, 2002 at 03:41:33PM -0800, David Sisson wrote:
> We have some cases when copying indexes that we'd like rsync to avoid
> the system cache when copying a chunk of data from some other machine.
> I am probably going to modify our own copy of rsync to do this, but if
> we could w
--relative has caused confusion to many people. If you could come up with
a patch and/or a change to the man page that made it easier to understand
and/or more useful I think it would be welcome.
- Dave Dykstra
On Wed, Dec 04, 2002 at 03:00:42PM -0500, Christopher Schanzle wrote:
> Hello, all.
Also, you'll probably want to use the --whole-file option of rsync to
minimize the amount of samba network traffic (although J.W. is probably
right about the main problem being in perl). That's the default in later
versions of rsync when copying between two local file paths.
- Dave Dykstra
On Tu
The problem is in your use of "-e rsh"; --blocking-io is assumed if
the -e value is equal to the RSYNC_RSH define which is usually "remsh"
on solaris but maybe it isn't on solaris 2.8. The --blocking-io option
is required for most versions of rsh, but it's sometimes difficult for
rsync to know whe
On Thu, Dec 05, 2002 at 07:39:53AM -0500, Green, Paul wrote:
> But is there an OS-independent way to set this attribute? I haven't
> memorized the POSIX standard, but I don't recall seeing a way to set or get
> such an attribute.
Fyi: Solaris has directio(3C), FreeBSD has open(..., O_DIRECT).
--
I have an Empeg car MP3 player (http://www.empeg.com) that is
running an embedded version of Linux on a StrongARM CPU.
When using rsync 2.5.5 on Linux/ARM and rsync 2.5.5 on Linux/x86
to transfer mp3 files, it appears file are always transmitted as
a whole, even if only the timestamp differs.
Fi
please UNSUBSCRIBE and REMOVE me from all your lists.
The message you sent was not received.
It was rejected by the mail server because it looked like
SPAM (unsolicited bulk advertisement). If you are receiving this
message in error, please try resending your message with '332762'
in t
Personally I don't see why see why replacing a file with a symbolic
link is any more dangerous than replacing it with a different file.
Doesn't it back up the file if you use the --backup option? If you use
the --update option rsync shouldn't replace any file or symlink that is
newer than the eith
From: David Sisson [mailto:[EMAIL PROTECTED]] asks:
> [...]
> If we could write directly to the disk using direct-io (or from for that
> matter) we could avoid polluting the operating system's buffer cache
> before we're ready to use the new data. Obviously this feature isn't
> tied to Direct-IO,
20 matches
Mail list logo
