Try Understand Error

2004-03-15 Thread Vladimir Potapov
I'm using server on OpenBSD 3.4 to backuping data from remote server via rsync.On backup server I am install rsync-2.5.6 and on remote machine rsync-2.5.7 (RedHat 8.0) . For backuping data I'm using the following command : rsync -av -e ssh [EMAIL PROTECTED]:/var/backup/ALL-15-Mar.tar

rsyncd without syslog

2004-03-15 Thread Torsten Senf
Hi, is it possible to use the rsyncd Daemon without any logging. I would like to make a network synchronization on a specific directory in a small network (10 Hosts) . These synchronisation should happen every 10 secounds. My logfile increases to fast with the logging option therefore it is

'Invalid cross-device link' message on sparc

2004-03-15 Thread Werner Augustin
Hi, I've got problems with a symlink to another device in a directory used with '--link-dest'. I've got something like [EMAIL PROTECTED]:/tmp/rsync% ls -alR .: total 16 drwxr-xr-x4 augustin augustin 4096 Mar 15 12:07 ./ drwxrwxrwt4 root root 4096 Mar 15 10:56 ../

Re: 'Invalid cross-device link' message on sparc

2004-03-15 Thread Werner Augustin
Werner Augustin [EMAIL PROTECTED] writes: and when I try: e/ dest building file list ... done created directory dest ./ dir/ link /tmp/rsync/unusable_link-dest/dir/foo = dir/foo : Invalid cross-device link wrote 106 bytes read 20 bytes 252.00 bytes/sec total size is 9 speedup is

Re: 'Invalid cross-device link' message on sparc

2004-03-15 Thread Tim Conway
tmp/rsync/unusable_link-dest/dir/foo and dir/foo are on different filesystems. --link-dest= makes hard links - new directory entries pointing at the same inodes. Directory entries don't have any way to specify the device containing the filesystem. It's assumed that it's the same device

Re: rsync wont work

2004-03-15 Thread Tim Conway
There we are. Thanks. OK, you're using ssh, and you can ssh in, so we can assume you're getting in. Now, ssh [EMAIL PROTECTED] and then which rsync is different from ssh [EMAIL PROTECTED] which rsync. ssh without a command starts a login shell, and you get your full environment. With a

Re: suppressing motd without decreasing verbosity

2004-03-15 Thread Tim Conway
The simplest solution is to not have the rsyncd demand that clients display the motd. motd is not considered part of verbosity, so the only way to shut it off on the client side is to have the client shut all the way up. +++ [EMAIL PROTECTED]

Re: rsyncd without syslog

2004-03-15 Thread Tim Conway
First, good luck with your dynamic data... it sounds like you might be wanting a distributed filesystem instead, but on to the question: In your rsyncd.conf log file = /dev/null That stops sending to syslog, and throws away the log data (rather than storing it in a file). Oh, and if you hadn't

Re: MD4 checksum_seed

2004-03-15 Thread Eran Tromer
Hi, On 2004/03/15 03:49, Donovan Baarda wrote: Note that, above, block hash collisions are very easy to find if you know checksum_seed. The rolling Fletcher checksum1 is trivially defeated. To defeat the k-bit truncated MD4 checksum2, just keep generate random blocks having the same checksum1

Re: suppressing motd without decreasing verbosity

2004-03-15 Thread Akop Pogosian
Yes, that's a possibility but unfortunately, I don't have control of the remote site. I am surprised there is no way to to do this with the client. -akop On Mon, Mar 15, 2004 at 08:04:47AM -0700, Tim Conway wrote: The simplest solution is to not have the rsyncd demand that clients display

Re: [patch] Correct configure test for sin_len to compile on Tru64 Unix

2004-03-15 Thread Shinichi Maruyama
wayned So, it looks like we need 2 configure tests and separate defines for wayned sa_len and sin_len. wayned How about the appended patch? This applies to the very latest CVS wayned source and would require the running of autoconf and autoheader wayned after applying it. I use rsync

Re: [patch] Correct configure test for sin_len to compile on Tru64 Unix

2004-03-15 Thread Wayne Davison
On Tue, Mar 16, 2004 at 10:01:19AM +0900, Shinichi Maruyama wrote: This OS has sin_len in struct sockaddr_in. But after configure, HAVE_SOCKADDR_SIN_LEN remains undef in config.h. Needs patch like this ? Yup -- much appreciated! I've checked in your fix, plus an extra cleanup of

Re: MD4 checksum_seed

2004-03-15 Thread Donovan Baarda
On Tue, 2004-03-16 at 10:44, Eran Tromer wrote: Hi, On 2004/03/15 03:49, Donovan Baarda wrote: [...] Just to be sure, I wrote a quickdirty collision search code for the rsync and librsync hashes. I used a generic collision-finding algorithm (namely Gabriel Nivasch's multistack variant of

CVS update: rsync

2004-03-15 Thread Wayne Davison
Date: Tue Mar 16 01:26:28 2004 Author: wayned Update of /data/cvs/rsync In directory dp.samba.org:/tmp/cvs-serv9446 Modified Files: configure config.h.in Log Message: Regenerated. Revisions: configure 1.178 = 1.179

CVS update: rsync

2004-03-15 Thread Wayne Davison
Date: Tue Mar 16 01:26:31 2004 Author: wayned Update of /data/cvs/rsync In directory dp.samba.org:/tmp/cvs-serv9462 Modified Files: clientname.c socket.c Log Message: Changed HAVE_SOCKADDR_SIN_LEN to HAVE_SOCKADDR_IN_LEN. Revisions: clientname.c1.16 = 1.17

CVS update: rsync/lib

2004-03-15 Thread Wayne Davison
Date: Tue Mar 16 01:26:36 2004 Author: wayned Update of /data/cvs/rsync/lib In directory dp.samba.org:/tmp/cvs-serv9479/lib Modified Files: getaddrinfo.c getnameinfo.c Log Message: Changed HAVE_SOCKADDR_SA_LEN to HAVE_SOCKADDR_LEN. Revisions: getaddrinfo.c 1.19 = 1.20

CVS update: rsync

2004-03-15 Thread Wayne Davison
Date: Tue Mar 16 01:26:40 2004 Author: wayned Update of /data/cvs/rsync In directory dp.samba.org:/tmp/cvs-serv9542 Modified Files: configure.in Log Message: Fixed the test for sin_len as noted by Shinichi Maruyama. Changed the define name generated for this test and the sa_len