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
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 D
--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,
t
> > such an attribute.
>
> Fyi: Solaris has directio(3C), FreeBSD has open(..., O_DIRECT).
What about Linux? There's an O_DIRECT but the comment in asm/fcntl.h says
it is currently ignored.
- Dave Dykstra
--
To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html
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
ple you gave I get the error
client: nothing to do: perhaps you need to specify some filenames or the
--recursive option?
- Dave Dykstra
On Wed, Dec 04, 2002 at 11:34:02AM -, David Flood wrote:
> Before I start let me say I'm a relative newbie to rsync so bear with me. I
nsfer().
Is anybody interested in writing a patch and testing it?
- Dave
On Thu, Dec 05, 2002 at 08:20:51AM -0600, Dave Dykstra wrote:
> 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
I disagree that the number of rsync bugs is too low to bother tracking
in a bug tracking system. I think that a lot of things have been posted
that are genuine bugs but have been forgotten about because none of the
developers have had the time to track them. If bug reports were all
dealt with qui
s.
I'll go ahead and take out the check for copy_links.
- Dave Dykstra
On Thu, Dec 05, 2002 at 05:04:38PM -0600, Bo Kersey wrote:
> 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
Is /home now a symlink? The fact that the "is uptodate" message is only
appearing on a single file ("home") makes me think it is not recursing
into the directory. If so, just change the end of your command line to
... /home/ slave:/home/
- Dave
On Mon, Dec 09, 2002 at 04:36:41PM +0100, Mark
On Sun, Dec 08, 2002 at 11:48:57PM -0800, Craig Barratt wrote:
> I've been studying the read and write buffering in rsync and it turns
> out most I/O is done just a couple of bytes at a time. This means there
> are lots of system calls, and also most network traffic comprises lots
> of small packe
attempt to go outside of the top module. However, I believe, but am not
sure, that if --copy-links is used with "use chroot = no" it should pull
in files pointed to by symlinks from outside the top. Try it out.
- Dave Dykstra
On Fri, Dec 13, 2002 at 01:44:30PM -0500, Kevin Minder w
http://lists.samba.org/pipermail/rsync/2002-September/008227.html
is safer. As far as I know we've still never heard from Tridge why he
introduced the code that caused the bug.
- Dave Dykstra
--
To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync
Before posti
When preserve_perms is not set, rsync sets a default permission based on
the original permissions and the umask. A comment in flist.c says that is
what GNU cp does, so that's why rsync does it. Comments in generator.c
and receiver.c indicate that if a file already exists and preserve_perms
isn't
/gzip-rsyncable.diff.
According to my email record, I once found a workaround by deleting the
"|| tx_strm.avail_in != 0" on line 285 of token.c. That change has not
been put into 2.5.5 or into a later development version because it was
unknown what the side effects were.
- Dave Dykstra
if (!optString[0])
> > return POPT_ERROR_BADOPT;
...
> I don't feel brave enough to commit the popt/popt.c change without input from
> others.
The patch seems harmless, although I'm not sure it's the best style.
How about making strcpy a macro instead
;t really help me in my
> situation, where permissions cannot be altered because of the network
> mount they are being written to.
>
> Does it make sense to impliment a "don't touch permissions" flag?
>
> On Tue, 2002-12-24 at 05:08, Dave Dykstra wrote:
> > When pr
nal permissions and umask.
>
> On Tue, 2002-12-31 at 07:58, Dave Dykstra wrote:
> > What do you mean, "altered"? Do the destination files already exist?
> > It is supposed to preserve existing permissions on destination files
> > when you don't use -p.
> &g
e a bad idea, but when writing to a share with forced
> permissions
>
> I'm actually a bit surprised nobody else has run into this.
>
> On Tue, 2002-12-31 at 13:20, Dave Dykstra wrote:
> > Then what would you expect it to do? I'm guessing your only problem is
See the BATCH MODE section in the rsync 2.5.5 man page. It's stil pretty
new and experimental, so it may not do what you want, but currently it's the
best that rsync can do.
- Dave Dykstra
On Wed, Jan 01, 2003 at 04:39:06PM -, va_public <[EMAIL PROTECTED]>
wrote:
>
That indeed is not right, and it appears that other people have noticed the
problem before but nobody has come up with a fix. The problem must be related
to the unsafe_symlink() function in util.c. Martin noticed a strange thing in
the code (see http://lists.samba.org/pipermail/rsync/2002-April/0
What Hadmut wants is the oft-requested and discussed "files-from" option
that I once offered to write but haven't been able to get to. Andy Schor
in http://lists.samba.org/pipermail/rsync/2001-November/005272.html posted
a patch for something similar but it only worked when the sender was on the
l
I've never seen anybody suggest any other value for --modify-window than "2".
Does 90 really work better than 2? My understanding is that PC-style
filesystems do not have 1 second timestamp granularity and so round the
times up or down slightly.
- Dave Dykstra
On Fri, Jan 03, 200
output of the -v option and run
xargs chmod on all files that have been touched.
- Dave Dykstra
On Thu, Jan 02, 2003 at 12:47:18PM +1100, [EMAIL PROTECTED] wrote:
>
> This appears to be a feature :-)
>
> I'm running rsync 2.5.5 on Solaris 8, and testing transferring
>
ctory
structure the directories were replaced by symlinks? I have not yet been
able to come up with an example where --force makes a difference when
using --delete and -r (or -a). Refer to
http://lists.samba.org/pipermail/rsync/2002-January/005971.html
- Dave Dykstra
--
To uns
Even though rsync maintenance isn't as bad as wget's, the maintainers
are all VERY part time so that is a big part of the problem. Most of us
don't have ipv6 systems to test things on. Can you vouch for the quality
of the patch? I was able to get it with
wget --passive
ftp://ftp.linux-ipv6
ict rsync
operations to only those defined by rsyncd.conf.
- Dave Dykstra
On Sun, Jan 05, 2003 at 01:07:30PM -0500, Aaron Morris wrote:
> I do not think you can use it with ssh, but if you use rsync in rsync
> mode (::) instead of just an interface to rsh (:), you can limit the
> direc
We've been calling this option --files-from rather than --file-list,
to be like the GNU tar option.
On Sun, Jan 05, 2003 at 09:55:50AM -0800, Wayne Davison wrote:
> On Sat, Jan 04, 2003 at 05:03:02PM -0800, jw schultz wrote:
> > that would produce destloc/srcdir/
> > when you might want a copy
That sounds reasonable to me that rsync shouldn't try to preserve those
extra bits without -p. Try making a patch and seeing if that works.
I don't have Samba set up, but on a vfat filesystem on Linux rsync is
doing even worse because after the initial file creation it does a
"fchmod(fd, 0600)" w
On Wed, Jan 08, 2003 at 12:25:15AM +0100, Bert Vermeulen wrote:
> On Tue, 7 Jan 2003, Dave Dykstra wrote:
>
> > Even though rsync maintenance isn't as bad as wget's, the maintainers
> > are all VERY part time so that is a big part of the problem. Most of us
> &g
On Wed, Jan 08, 2003 at 03:08:38PM +1100, [EMAIL PROTECTED] wrote:
>
>
> Thanks for the reply.
>
> I did see this on the to-do list, and thought that it might
> be a preferable solution (just a bit more work).
> It would be messy to do the xargs stuff as I am running rsync
> over ssh with restri
case that --delete is used (and so far I have been unable to find any
such case), I think it would make sense for --force to be automatically
turned on by --delete.
- Dave
On Wed, Jan 08, 2003 at 07:39:22AM -0700, David Garamond wrote:
> Dave Dykstra wrote:
> >Could you please post you
I've never heard of a name length limit. One operating system(s) and rsync
version(s) are you using?
- Dave
On Wed, Jan 08, 2003 at 07:32:19AM -0800, elijah reyen wrote:
> Does rsync has directory name length limit? I was trying to rsync a directory that
>has the name length of 34 characters a
On Thu, Jan 09, 2003 at 01:02:29PM +0100, Lapo Luchini wrote:
> Uhm... rsync developers: what do you think about changing the default
> modify-window in the Cygwin platform?
> It seems to me that many problems people have are just because of the
> granularity of timestamp.
> Maybe changing the de
On Thu, Jan 09, 2003 at 05:52:43PM +0100, Lapo Luchini wrote:
> Dave Dykstra wrote:
>
> >it would fail if it were
> >talking to a release of rsync that is too old to recognize the
> >option[...]. The surprise factor on that may be too much to make it
> >worthwhile
I am preparing for making 2.5.6pre1 today and decided to submit David
Staples patch with a little rework. Here's the version I submitted.
- Dave Dykstra
--- main.c~ Thu Aug 1 15:46:59 2002
+++ main.c Thu Jan 9 12:43:55 2003
@@ -26,6 +26,16 @@
extern struct stats stats;
exter
local/src/* /tmp/localhost/daily.0
Remove the '*'. In order for rsync to delete a file, it needs to deal
with the directory that the files are in and the '*' tells it to only
deal with the files in the directory.
- Dave Dykstra
--
To unsubscribe or change options: http:/
cess.c. I also updated the rsyncd.conf.yo documentation
to allow for IP address of the IPv6 form.
I have not tested this, I hope it works.
- Dave
On Wed, Jan 08, 2003 at 08:24:13AM -0600, Dave Dykstra wrote:
> On Wed, Jan 08, 2003 at 12:25:15AM +0100, Bert Vermeulen wrote:
> > On Tu
ting
inherited from its parent, but it doesn't help to re-set it in the child.
Nevertheless, I'm not sure whether or not the sigusr2_handler function
is getting called in the child. I'd appreciate some help with this if
anybody else thinks they can figure it out.
- Dave Dykst
On Fri, Jan 10, 2003 at 12:46:13AM -0800, Wayne Davison wrote:
> On Thu, Jan 09, 2003 at 05:09:07PM -0600, Dave Dykstra wrote:
> > I'm stuck on a problem that some machines on build.samba.org are
> > showing on the 'chgrp' test.
>
> I've checked in a fix
I checked in this patch.
- Dave
On Thu, Jan 09, 2003 at 06:41:19PM -0800, jw schultz wrote:
> I just did a make clean to tidy up a bit and found four
> objects were missed. The seem to belong to the CHECK_PROGS
> set. Not sure where best to put them so created a
> CHECK_OBJS variable and added
Ok, I agree --modify-window should default to 2 (or 1 if that's all that's
really needed) on cygwin. However, I don't like os-specific defines.
That _WIN32 we've got there is the only one currently in the code, and
there's no occurrances of __CYGWIN__. I'd rather have a configure.in
rule for it.
On Fri, Jan 10, 2003 at 11:33:00AM -0800, Wayne Davison wrote:
> On Fri, Jan 10, 2003 at 01:23:45PM -0500, Green, Paul wrote:
> > The following patch still applies cleanly to the current cvs copy of rsync.
>
> Or did before the most recent Makefile.in changes. It's easy to merge
> this one proble
On Sun, Jan 12, 2003 at 11:51:07PM +0100, Bert Vermeulen wrote:
> On Fri, 10 Jan 2003, Bert Vermeulen wrote:
>
> > On Thu, 9 Jan 2003, Dave Dykstra wrote:
> >
> > > I went ahead and submitted Hideaki's patch pretty much as is. I took off
> > > the if
On Sat, Jan 11, 2003 at 11:19:33AM -0800, Ben wrote [off list]:
> On Tue, 2003-01-07 at 14:49, Dave Dykstra wrote:
> > That sounds reasonable to me that rsync shouldn't try to preserve those
> > extra bits without -p. Try making a patch and seeing if that works.
> >
>
iles that
contains a duplicate name (if it sorts to the end of the file
list) and using --delete. (Wayne Davison)
* Fixed a bug that caused rsync to lose the exit status of its child
processes and sometimes return an exit code of 0 instead of showing
an error. (David R
On Mon, Jan 13, 2003 at 01:59:47PM -0500, Scott Evans wrote:
> > Known issues that will probably need to be resolved before the final
> > release:
> > [...]
>
> Is there any interest in trying to hunt down the "linux -> cygwin
> rsync hanging" problem I'm consistently seeing before this release?
>
On Mon, Jan 13, 2003 at 11:00:58AM -0800, Ben wrote:
> Well that's annoying. I've tried changing the encoding of this
> attempt... maybe it'll get through this time.
Yes, it came through better this time.
> As a rule of thumb, I think silent errors a very bad idea. It means
> things might not be
Craig, I'd like to get your patch into the 2.5.6 patches directory.
Could you please make sure it applies cleanly onto version 2.5.6pre1 (see
news on http://rsync.samba.org home page if you haven't been following
the mailing list) and repost it?
Thanks,
- Dave Dykstra
On Wed, Dec 11,
2.5.6pre1 bombs on Sunos4 gcc with these errors
popt/popthelp.c: In function `singleOptionDefaultValue':
popt/popthelp.c:137: invalid operands to binary +
popt/popthelp.c:141: invalid operands to binary +
popt/popthelp.c:145: invalid operands to binary +
popt/popthelp.c:149: inv
On Mon, Jan 13, 2003 at 09:03:23PM -0500, Michael Sterrett -Mr. Bones.- wrote:
> Greetings -
>
> In trying to get rsync-2.5.6pre1 working on DYNIX/ptx, I found I
> needed to pass ac_cv_lib_inet_connect=no to configure in order for
> it actually create a properly configured config.h fil
On Tue, Jan 14, 2003 at 10:24:04AM -0600, Dave Dykstra wrote:
> 2.5.6pre1 bombs on Sunos4 gcc with these errors
> popt/popthelp.c: In function `singleOptionDefaultValue':
> popt/popthelp.c:137: invalid operands to binary +
> popt/popthelp.c:141: invalid operands to bi
On Tue, Jan 14, 2003 at 01:21:29PM -0800, Wayne Davison wrote:
> On Tue, Jan 14, 2003 at 11:02:44AM -0500, Andrew J. Schorr wrote:
> > I am attaching an updated version of my patch to allow you to specify
> > a list of files to transfer.
>
> Cool. I'm looking into making this work when fetching f
On Tue, Jan 14, 2003 at 05:29:06PM -0500, Andrew J. Schorr wrote:
> Hi,
>
> This is perhaps a stupid question. I apologize in advance if it's already
> been covered, but I'm stumped...
>
> I'm using rsync to backup some file systems to a remote host.
> The transport is openssh-2.9.9p2.
>
> The
Below is the patch I just checked in to fix --copy-unsafe-links. As far
as I can tell it has been broken for years, ever since I first put it in.
It bothers me a bit that I can't figure out why I went through the
trouble and mess at the time to introduce a global variable to compare
to wrong infor
On Wed, Jan 15, 2003 at 05:12:21PM -0500, Andrew J. Schorr wrote:
> On Wed, Jan 15, 2003 at 09:27:37AM -0600, Dave Dykstra wrote:
> > Unfortunately I don't think anybody is going to be able to tell you.
> > I've not heard of anybody lately posting a similar problem.
Martin left off some context that might confuse some list readers. I
had inquired about how to sign the pre-release tarball. I signed
2.5.6pre1 with my personal key, but Martin suggested there be a team key.
On Thu, Jan 16, 2003 at 10:42:53AM +1100, Martin Pool wrote:
> [replied to list]
>
> T
debug this further.
- Dave
On Fri, Jan 10, 2003 at 01:49:37PM -0600, Dave Dykstra wrote:
> On Fri, Jan 10, 2003 at 11:33:00AM -0800, Wayne Davison wrote:
> > On Fri, Jan 10, 2003 at 01:23:45PM -0500, Green, Paul wrote:
> > > The following patch still applies cleanly to the current
Thanks for the reminder. I checked in the second version.
- Dave
On Wed, Oct 09, 2002 at 12:45:03PM +0300, Sviatoslav Sviridov wrote:
> On Wed, 9 Oct 2002 10:03:33 +0200 (CEST)
> Ruediger Oertel <[EMAIL PROTECTED]> wrote:
>
> > Hi,
> >
> > we ran into a little problem with rsync-2.5.5.
> >
>
On Wed, Jan 15, 2003 at 02:24:10PM -0800, jw schultz wrote:
> On Wed, Jan 15, 2003 at 10:27:31AM -0600, Dave Dykstra wrote:
> > In my research into this I also found that 2-1/2 years ago somebody
> > posted a patch that included a fix for this buried in it, and that I
> > had
On Wed, Jan 15, 2003 at 02:49:08PM -0800, jw schultz wrote:
> On Wed, Jan 15, 2003 at 10:03:33AM -0800, Wayne Davison wrote:
> > On Tue, Jan 14, 2003 at 07:57:48PM -0800, jw schultz wrote:
> > > with the -r or -a options does this [recurse] on
> > > directories in the --files-from list?
> >
> > Ye
deploying files as if the umask was still 022. Come to find out, the
> box had been rebooted the night before; inetd was never restarted when
> the umask was changed (and usually is never restarted) and was still
> operating with a umask of 022.
>
> Dave Dykstra wrote:
> | On Wed, Ja
The patch from 2-1/2 years ago for changing copy-unsafe-links to follow
unsafe links on the destination side also included essentially this patch.
When I looked at it, however, I asked why in the world is unsafe_symlink()
doing strdup() in the first place. I think you could get rid of the
calls to
On Thu, Jan 16, 2003 at 03:44:44PM -0500, Scott Mcdermott wrote:
> Dave Dykstra on Thu 16/01 14:33 -0600:
> > The patch from 2-1/2 years ago for changing copy-unsafe-links to follow
> > unsafe links on the destination side also included essentially this patch.
>
> just to be
u, Jan 16, 2003 at 05:34:25PM -0800, Wayne Davison wrote:
> On Thu, Jan 16, 2003 at 02:33:26PM -0600, Dave Dykstra wrote:
> > I think you could get rid of the calls to strdup() and the new local
> > variables and possibly do a couple casts inside the function instead.
>
> You
On Thu, Jan 16, 2003 at 04:08:01PM -0500, Scott Mcdermott wrote:
> Dave Dykstra on Thu 16/01 14:57 -0600:
> > > > The patch from 2-1/2 years ago for changing copy-unsafe-links to
> > > > follow unsafe links on the destination side also included
> > > > essen
On Thu, Jan 16, 2003 at 03:18:34PM -0600, Dave Dykstra wrote:
> On Thu, Jan 16, 2003 at 04:08:01PM -0500, Scott Mcdermott wrote:
> > Dave Dykstra on Thu 16/01 14:57 -0600:
> > > > > The patch from 2-1/2 years ago for changing copy-unsafe-links to
> > > > >
On Thu, Jan 16, 2003 at 11:14:50PM -0800, Wayne Davison wrote:
> On Thu, Jan 16, 2003 at 07:06:05PM -0800, jw schultz wrote:
> > [...] and that entries therein are not flattened like they would be on
> > the command-line (sans -R).
>
> But they *are* flattened exactly like on the command-line, at
ay, in the future I would appreciate it if you would post bugs to
the rsync mailing list instead of to me because other rsync team members
should see these things too and might be able to reply faster than me.
- Dave Dykstra
On Sat, Jan 18, 2003 at 06:21:28PM -0500, Brian Poole wrote (in private em
On Fri, Jan 17, 2003 at 12:31:26AM +0100, Bert Vermeulen wrote:
> On Mon, 13 Jan 2003, Dave Dykstra wrote:
>
> > I don't understand enough how that syntax works in order to be able
> > to write an explanation for people. Could you please try to write
> > something up
I submitted a patch similar to what Max suggested. Nobody came up with
a definitive answer on whether the modify-window default should be 1 or
2 so I left it at 2.
- Dave
On Fri, Jan 10, 2003 at 06:27:31PM -, Max Bowsher wrote:
> Dave Dykstra wrote:
> > Ok, I agree --modify-wind
Thanks for the quick tutorial. I submitted your patch, changing eth0
to link1 as Hideaki suggested.
- Dave
On Mon, Jan 20, 2003 at 06:35:09PM +0100, Bert Vermeulen wrote:
> On Mon, 20 Jan 2003, Dave Dykstra wrote:
>
> > On Fri, Jan 17, 2003 at 12:31:26AM +0100, Bert Vermeulen wro
On Sat, Jan 18, 2003 at 12:25:05AM -0800, Wayne Davison wrote:
> On Fri, Jan 17, 2003 at 11:39:31PM -0800, Craig Barratt wrote:
> > If mkstemp() fails (for various reasons, including the directory not
> > existing) then fd == -1. So the first if () executes, which flushes
> > the data and does a c
I submitted a change to ignore errors from chmod when -p is not set.
GNU cp does the same thing.
- Dave Dykstra
On Mon, Jan 13, 2003 at 01:13:48PM -0800, jw schultz wrote:
> On Mon, Jan 13, 2003 at 02:38:29PM -0600, Dave Dykstra wrote:
> > On Mon, Jan 13, 2003 at 11:00:58AM -0800,
be 1?
Changes since 2.5.5pre1:
ENHANCEMENTS:
* Set the default value of --modify-window to 2 on Cygwin. (Max Bowsher)
* Ignore errors from chmod when -p/-a/--preserve-perms is not set.
(Dave Dykstra)
BUG FIXES:
* Fixed the file-name duplicate-removal code when dealin
On Tue, Jan 21, 2003 at 11:37:12AM -, Max Bowsher wrote:
> Dave Dykstra wrote:
> > Changes since 2.5.5pre1:
> >
> > ENHANCEMENTS:
> >
> > * Set the default value of --modify-window to 2 on Cygwin. (Max
> > Bowsher)
>
> No, not me. I only
On Wed, Jan 22, 2003 at 02:49:03AM +0100, wim delvaux wrote:
> WHY OH WHY does rsync SEND and CREATE a file called RepositoryPath ALTHOUGH
> the rsync is called like
>
> rsync "--exclude=*.bup RepositoryPath" ...
>
> can ANYBODY explain.
It doesn't happen for me. Is your "rsync" command actual
On Wed, Jan 22, 2003 at 03:42:06AM +0100, wim delvaux wrote:
...
> > > ALSO when you specify an exclude list on the server in the rsyncd.conf
> > > file and you call rsync with the --delete option WHY DO THE FILES that
> > > SHOULD BE EXCLUDED get deleted ??
> > >
> > > Jeeez, what a bummer
> > > W
Look for errors in /var/log/rsyncd.log. For security reasons they are
not all passed to the client.
- Dave
On Wed, Jan 22, 2003 at 06:52:33PM -0200, Breno Cardoso Perucchi wrote:
> Hello,
>
> I'm trying to do my rsync to copy a mirror of my site in another webserver.
> I am trying to use RSYNCD
On Tue, Jan 21, 2003 at 08:00:51PM -0801, Jos Backus wrote:
> On Mon, Jan 20, 2003 at 10:19:42PM -0600, Dave Dykstra wrote:
> > The second rsync-2.5.6 pre-release version is now available at:
>
> There's the popt-1.7 update (with Dave's sprintf() workaround) at
>
I'm not sure why it would really need to know the size, but given that
it wants it, can you open the file and lseek to the end of it?
- Dave Dykstra
On Thu, Jan 23, 2003 at 09:17:04AM +0100, David Heremans wrote:
> Hello,
>
> I'm looking for some assistance in modif
With file sizes over 2GB I'd suspect problems with >31-bit numbers being
returned from stat() et. al. The rsync version you have on AIX is very
old, and more recent versions handle large files better. The first thing
to do is to upgrade rsync your AIX machine.
- Dave
On Thu, Jan 23, 2003 at 01:
tf-8&threadm=a4vfnh%242ec%241%40FreeBSD.csie.NCTU.edu.tw&rnum=1&prev=/groups%3Fq%3Drsync%2Bon%2Bcygwin%2B-%2Btextmode%2Bconfig%2Bfiles%26num%3D50%26hl%3Den%26lr%3D%26ie%3DUTF-8%26oe%3Dutf-8%26sa%3DN%26tab%3Dwg
> > >
> > > I'm mostly talking about (4) - others are
On Fri, Jan 24, 2003 at 08:57:02AM +0200, Ville Herva wrote:
> On Thu, Jan 23, 2003 at 01:55:40PM -0600, you [Dave Dykstra] wrote:
> > Why did you skip the fopen in log.c, which appends to the log file?
>
> I thought about that for a while. My reasoning was that the log file is
n anybody give me an argument for putting in the
calls to "shutdown()" anyway? I would make it only happen on Cygwin,
because it is unknown if they will cause harm on other platforms.
- Dave Dykstra
--
To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rs
On Sat, Jan 25, 2003 at 12:10:39AM -, Max Bowsher wrote:
> Dave Dykstra wrote:
> > While doing the tests we too experienced hangs at the end of copies.
> > We were going over openssh from a Solaris 9 box to Windows 2000
> > Cygwin.
> > We tried the test from
>
On Fri, Jan 24, 2003 at 04:02:28PM -0800, jw schultz wrote:
> On Fri, Jan 24, 2003 at 04:49:20PM -0700, Bill Geddes wrote:
> > Am I running out of memory on the source server? Seems perhaps more
> > plausible than on the client - it has nothing going on and 1Gb RAM.
> > The server has rsync versio
I submitted the patch.
Thanks Marc & Brian.
- Dave Dykstra
On Thu, Jan 23, 2003 at 08:29:40PM -0500, Brian Poole wrote:
> Hello,
>
> There is still a problem with the _exit_cleanup() function in
> cleanup.c despite the patch that was put in last week that prevented
> recu
Alright. Max, could you quickly verify if the latest CVS version works
OK for you on Cygwin?
It's better to always handle all three styles of line terminations anyway,
because there are other situations than systems that have O_TEXT defined
where it might be wanted, for example a Linux system tha
On Sun, Jan 26, 2003 at 08:54:19PM -, Max Bowsher wrote:
> Dave Dykstra wrote:
> > Alright. Max, could you quickly verify if the latest CVS version
> > works OK for you on Cygwin?
>
> What, in particular? I'm not a very good testcase, because I use binary
>
Is there any reason why caching programs would need to set the
value, rather than it just being a fixed value? I think it is hard
to describe what this is for and what it should be set to. Maybe a
--fixed-checksum-seed option would make some sense, or for a caching
mechanism to be built in to rsy
On Sun, Jan 26, 2003 at 02:46:43PM -0800, Craig Barratt wrote:
> > Is there any reason why caching programs would need to set the
> > value, rather than it just being a fixed value?
> > I think it is hard to describe what this is for and what it should be
> > set to. Maybe a --fixed-checksum-seed
On Sat, Jan 25, 2003 at 06:32:08PM +0100, Greger Cronquist wrote:
> --- Max Bowsher <[EMAIL PROTECTED]> skrev: > Dave Dykstra
> wrote:
>
> > I'm using the current Cygwin release
> > (rsync-2.5.5-2). That is rsync-2.5.5,
> > with an added msleep(30) whic
Well I was hoping to get the 2.5.6 out today, but I think I made too many
Cygwin changes this evening for comfort and I'd like to allow one more
day of testing. Cygwin users, please test as much as you can and post
any problems.
- Dave Dykstra
--
To unsubscribe or change options:
On Mon, Jan 27, 2003 at 10:46:16AM +0100, Lapo Luchini wrote:
> Dave Dykstra wrote:
>
> >>What, in particular? I'm not a very good testcase, because I use binary
> >>mounts and unix line endings everywhere.
> >>
> >>It compiles and does sync
On Fri, Jan 24, 2003 at 05:18:07PM -0600, Dave Dykstra wrote:
> I had a friend run some Cygwin tests and we found that --modify-window=1
> works just as well as --modify-window=2 on FAT filesystems to copy files
> from Unix and detect the difference in granularity. FAT filesystems alwa
On Mon, Jan 27, 2003 at 04:38:09PM -, Max Bowsher wrote:
> Dave Dykstra wrote:
> > This modify-window default of 1 has been causing some trouble on the
> > rsync test suite on the Cygwin test machine on build.samba.org. The
> > problem is that some files get created a
On Mon, Jan 27, 2003 at 04:45:25PM -, Max Bowsher wrote:
> Dave Dykstra wrote:
> > On Mon, Jan 27, 2003 at 10:46:16AM +0100, Lapo Luchini wrote:
> >> I can test that before releasing cygwin's 2.5.6-1 package,
> >> unfortunately I have almost *no* free time unt
Thanks, you saved me some trouble. I put it in.
- Dave
On Mon, Jan 27, 2003 at 06:52:30PM -0800, jw schultz wrote:
> On Mon, Jan 27, 2003 at 03:57:16PM -0600, Dave Dykstra wrote:
> > On Mon, Jan 27, 2003 at 04:38:09PM -, Max Bowsher wrote:
> > > Dave Dykstra wrote:
&
On Mon, Jan 27, 2003 at 04:01:46PM -0600, Dave Dykstra wrote:
> On Mon, Jan 27, 2003 at 04:45:25PM -, Max Bowsher wrote:
...
> > Cygwin has gone through many minor versions since then. I suggest releasing
> > an rsync without the hack, but with a command line option to turn it o
401 - 500 of 806 matches
Mail list logo
