[rsync-announce] Graphical rsync!
On Tuesday 12 Mar 02, [EMAIL PROTECTED] writes: Hello, Something very much resembling a graphical win32-based front-end for rsync is available at http://sync2nas.sourceforge.net It is released under the BSD license for all to enjoy. A few caveats: * It reportedly only works on WinNT/Win2K. Win9x is being looked into at this time. * It is written in Perl/Tk, although all portability conceits were abandoned fairly early on, and it currently makes quite a few assumptions that only make sense under win32. It was subsequently turned into a win32 executable through the magic of ActiveState tools. * It is bundled with rsync 2.4.6 and a cygwin1.dll, which can be replaced with newer versions at whim. ... Are you also distributing the source to cygwin1.dll? It is illegal not to. Regards, David -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html
rsync 2.5.4 -v output (minor knit)
I noticed a difference in verbose output that appears to be unintentional. it first prints 'receiving file list ...', then builds the list and prints 'done\n'. I haven't figured out the exact conditions yet, but with multiple remote sources (remote shell expands) it sometimes prints the 'done\n' message multiple times. I have a script I use to sync up my dot-files with multiple files and excludes that prints the 'done\n' line 16 times. Is there a simple fix? People parsing the output of -v may want to be aware of this. I first saw it in 2.5.3. -Lee -- Law of Selective Gravity: An object will fall so as to do the most damage. -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html
map_ptr warning
Title: map_ptr warning I am using rsync-2.5.2.Solaris251.sparc from your site to synchronize from an old Solaris2.5.1 server in Nashville to a new Solaris8 server in Raleigh. I will air express tapes and use rsync to update. I am dealing with several hundred thousand files and a couple hundred gigabytes of data. I use rsync -avx --delete -e ssh old:/foo/bar/ /foo/bar 2 /var/log/rsynclog run as a cronjob on the new computer. Most of the files are transferred correctly. With a few files I get the file name followed the two copies of the line: Warning: unexpected read size of 0 in map_ptr in the log file. In at least most cases, the next pass gives the same message on the same file. The file size is sometimes larger on the target and may grow on additional passes. If I delete the file on the target the next pass will normally work correctly. I see no pattern of where the problem will strike. In some cases, the problem files are plain text with simple path and file names. Any ideas? Thanks, Charles Mount
Re: map_ptr warning
Charles,
Delivered-To: [EMAIL PROTECTED]
From: Charles Mount [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: map_ptr warning
MIME-Version: 1.0
X-BeenThere: [EMAIL PROTECTED]
X-Mailman-Version: 2.0.8
List-Help: mailto:[EMAIL PROTECTED]?subject=help
List-Post: mailto:[EMAIL PROTECTED]
List-Subscribe: http://lists.samba.org/mailman/listinfo/rsync,
mailto:[EMAIL PROTECTED]?subject=subscribe
List-Id: rsync user list rsync.lists.samba.org
List-Unsubscribe: http://lists.samba.org/mailman/listinfo/rsync,
mailto:[EMAIL PROTECTED]?subject=unsubscribe
List-Archive: http://lists.samba.org/pipermail/rsync/
Date: Wed, 13 Mar 2002 15:50:06 -0600
I am using rsync-2.5.2.Solaris251.sparc from your site to synchronize from
an old Solaris2.5.1 server in Nashville to a new Solaris8 server in
Raleigh. I will air express tapes and use rsync to update. I am dealing
with several hundred thousand files and a couple hundred gigabytes of data.
I use rsync -avx --delete -e ssh old:/foo/bar/ /foo/bar 2
/var/log/rsynclog run as a cronjob on the new computer.
Most of the files are transferred correctly.
With a few files I get the file name followed the two copies of the line:
Warning: unexpected read size of 0 in map_ptr in the log file.
In at least most cases, the next pass gives the same message on the same
file. The file size is sometimes larger on the target and may grow on
additional passes. If I delete the file on the target the next pass will
normally work correctly. I see no pattern of where the problem will strike.
In some cases, the problem files are plain text with simple path and file
names.
Any ideas?
I got the same errors. Upgrade rsync to 2.5.3 with updating batch.c file
diff -u -r1.13 batch.c
--- batch.c 6 Feb 2002 21:20:48 - 1.13
+++ batch.c 12 Mar 2002 06:16:49 -
@@ -396,7 +396,7 @@
struct sum_struct *s)
{
size_t i;
-unsigned int int_zero = 0;
+size_t int_zero = 0;
extern int csum_length;
fdb_open = 1;
Then, re-compile it. After I compiled the new version of rsync, it works perfectly.
Thanks,
Charles Mount
Jennifer
--
To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html
Should these errors matter?
Hi All, rsync-2.5.4 --- I'm getting these errors: gmake test echo WARNING: You need to run ./config.status --recheck WARNING: You need to run ./config.status --recheck gcc -I. -I. -O2 -DHAVE_CONFIG_H -Wall -W -I./popt -c tls.c -o tls.o tls.c: In function `list_file': tls.c:124: warning: int format, uid_t arg (arg 4) tls.c:124: warning: int format, gid_t arg (arg 5) tls.c:124: warning: int format, long int arg (arg 6) gcc -O2 -DHAVE_CONFIG_H -Wall -W -I./popt -o tls tls.o syscall.o lib/permstring.o -lresolv -lsocket -lnsl POSIXLY_CORRECT=1 TLS=`pwd`/tls rsync_bin=`pwd`/rsync srcdir=. ./runtests.sh ./runtests.sh running in /opt/src/rsync-2.5.4 rsync_bin=/opt/src/rsync-2.5.4/rsync srcdir=. scratchbase=/opt/src/rsync-2.5.4/testtmp PASS00-hello PASSchgrp PASSchown - daemon-gzip-download log follows building configuration /opt/src/rsync-2.5.4/testtmp.daemon-gzip-download/test-rsyncd.conf Running: /opt/src/rsync-2.5.4/rsync -avvz localhost::test-from/ /opt/src/rsync-2.5.4/testtmp.daemon-gzip-download/to/ opening tcp connection to localhost port 873 receiving file list ... push_dir .: Permission denied (3) rsync error: errors selecting input/output files, dirs (code 3) at main.c(317) rsync: connection unexpectedly closed (28 bytes read so far) rsync error: error in rsync protocol data stream (code 12) at io.c(151) - daemon-gzip-download log ends FAILdaemon-gzip-download - daemon-gzip-upload log follows building configuration /opt/src/rsync-2.5.4/testtmp.daemon-gzip-upload/test-rsyncd.conf Running: /opt/src/rsync-2.5.4/rsync -avvz /opt/src/rsync-2.5.4/testtmp.daemon-gzip-upload/from/ localhost::test-to/ opening tcp connection to localhost port 873 building file list ... expand file_list to 4000 bytes, did move done rsync: mkdir .: Permission denied rsync error: error in file IO (code 11) at main.c(285) rsync: connection unexpectedly closed (28 bytes read so far) rsync error: error in rsync protocol data stream (code 12) at io.c(151) - daemon-gzip-upload log ends FAILdaemon-gzip-upload PASSdaemon PASSdevices SKIPduplicates PASShands PASShardlinks PASSlongdir SKIPssh-basic - symlink-ignore log follows + build_symlinks fromdir=/opt/src/rsync-2.5.4/testtmp.symlink-ignore/from todir=/opt/src/rsync-2.5.4/testtmp.symlink-ignore/to + mkdir /opt/src/rsync-2.5.4/testtmp.symlink-ignore/from + date + ln -s referent /opt/src/rsync-2.5.4/testtmp.symlink-ignore/from/relative + ln -s /opt/src/rsync-2.5.4/testtmp.symlink-ignore/from/referent /opt/src/rsync-2.5.4/testtmp.symlink-ignore/from/absolute + ln -s nonexistent /opt/src/rsync-2.5.4/testtmp.symlink-ignore/from/dangling + ln -s ./rsync.c /opt/src/rsync-2.5.4/testtmp.symlink-ignore/from/unsafe + /opt/src/rsync-2.5.4/rsync -r /opt/src/rsync-2.5.4/testtmp.symlink-ignore/from/ /opt/src/rsync-2.5.4/testtmp.symlink-ignore/to skipping non-regular file absolute skipping non-regular file dangling skipping non-regular file relative skipping non-regular file unsafe + [ -f /opt/src/rsync-2.5.4/testtmp.symlink-ignore/to/referent ] + [ -d /opt/src/rsync-2.5.4/testtmp.symlink-ignore/to/from ] + [ -L /opt/src/rsync-2.5.4/testtmp.symlink-ignore/to/dangling ] ./testsuite/symlink-ignore.test: test: argument expected - symlink-ignore log ends FAILsymlink-ignore - overall results: 8 passed 3 failed 2 skipped overall result is 3 gmake: *** [check] Error 3 Do these errors matter? Should I install this version of rsync or leave it? Regards, Jie -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html
Re: Should these errors matter?
On 14 Mar 2002, Jie Gao [EMAIL PROTECTED] wrote: Hi All, rsync-2.5.4 I'm getting these errors: Thanks for sending the log. That really helps. Are you perhaps running 'make test' as root? That would probably explain the failure of daemon-gzip-download and daemon-gzip-upload, which have little bugs in this respect at the moment. Could you please try building and testing as some other account? And are you perhaps on a Solaris machine? There's some kind of problem on the Solaris shell with symlink-ignore.test. If you know sh and could sort out what we're doing wrong that would be nice. So overall it is probably safe to install it. Regards, -- Martin -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html
Re: Should these errors matter?
On Thu, 14 Mar 2002, Martin Pool wrote:
On 14 Mar 2002, Jie Gao [EMAIL PROTECTED] wrote:
Hi All,
rsync-2.5.4
I'm getting these errors:
Thanks for sending the log. That really helps.
Thanks for your reply.
Are you perhaps running 'make test' as root? That would probably
explain the failure of daemon-gzip-download and daemon-gzip-upload,
which have little bugs in this respect at the moment. Could you
please try building and testing as some other account?
You are exactly right: I was running as root. Changing as another
user got rid of the first two errors.
And are you perhaps on a Solaris machine? There's some kind of
problem on the Solaris shell with symlink-ignore.test. If you know sh
and could sort out what we're doing wrong that would be nice.
This is from Solaris 7's manual for if:
The -L option is a migration aid for users of other shells
which have similar options and may not be supported in
future releases.
and indeed it does not support this option in this very release!
So you need to use the -h flag for Solaris in the following in symlink-ignore.test:
OS=`/bin/uname -s`
RELEASE=`/bin/uname -r`
if [ $OS = SunOS -a \($RELEASE = '5.7' -o $RELEASE = '5.8'\) ]
then
if [ -h ${todir}/dangling ]
then
test_fail dangling symlink was copied
fi
if [ -h ${todir}/relative ]
then
test_fail relative symlink was copied
fi
if [ -h ${todir}/absolute ]
then
test_fail absolute symlink was copied
fi
fi
So overall it is probably safe to install it.
Thanks,
Jie
--
To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html
Re: Should these errors matter?
On Thu, Mar 14, 2002 at 05:00:35PM +1100, Jie Gao wrote: This is from Solaris 7's manual for if: The -L option is a migration aid for users of other shells which have similar options and may not be supported in future releases. and indeed it does not support this option in this very release! -L doesn't appear to work in Solaris 8 either. However, the latest relevant standard, ``The Open Group Base Specifications Issue 6, IEEE Std 1003.1-2001'' lists both -h and -L and says (at the end): CHANGE HISTORY Issue 6 The -h operand is added for symbolic links, and access permission requirements are clarified for the -r, -w, and -x operands to align with the IEEE P1003.2b draft standard. The normative text is reworded to avoid use of the term must for application requirements. The -L and -S operands are added for symbolic links and sockets. -- Jos Backus _/ _/_/_/Santa Clara, CA _/ _/ _/ _/ _/_/_/ _/ _/ _/_/ [EMAIL PROTECTED] _/_/ _/_/_/use Std::Disclaimer; -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html
posix me harder
People might find this entertaining and/or useful: http://www.gnu.org/manual/autoconf-2.52/html_chapter/autoconf_10.html With the help of Jos Backus I just discovered the answer to http://lists.samba.org/pipermail/rsync-cvs/2002-January/001271.html is that Sun's test(1) is breathtakingly broken when passed a dangling symlink: $ ln -s /nowhere bad $ ls -l bad lrwxrwxrwx 1 josb user8 Mar 13 20:10 bad - /nowhere $ if test -L bad; then echo bad; fi test: argument expected $ if test -h bad; then echo bad; fi bad $ -- Martin -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html
