Re: limiting metadata updates

2002-04-26 Thread Martin Pool

There's no way to do that at the moment; --chmod and --chown options
to set metadata in flight are on the todo list.  In fact I think
there's a patch around for chmod, though I seem to remember the last
version had a couple of shortcomings.

--
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: Handling of backup files - two new features proposed

2002-04-26 Thread Stefan Nehlsen

On Thu, Apr 25, 2002 at 04:47:36PM -0500, Dave Dykstra wrote:
 On Mon, Apr 01, 2002 at 06:14:38PM +0200, Michael Zimmermann wrote:
  1.) Setting owner and/or group of backup files.
  
  In our servers I'm using rsync to backup to a hot standby machine.
  The users have access to this backup-server too, so that they
  can retrieve older versions of their files. At the same time the backup
  copies should not count in the user's quota (and/or should only
  be deletable by root or a special group-admin).
  
  To accomplish this, the backup files get their user and/or group set to
  a special user and/or group in our local version of rsync.
  
  Two new options control this behaviour
  
   --backup-owner=USER
   --backup-group=GROUP
 
 
 I don't like that; I think it is too special purpose.  Can't you follow
 up the rsync with a find/chown?

no -- that would mess up timestamps

But you are right there are too many options.


Stefan
-- 
Stefan Nehlsen | ParlaNet Administration | [EMAIL PROTECTED] | +49 431 988-1260

-- 
To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html



AW: rsync raising an IO error for an excluded file

2002-04-26 Thread Martin Bene

Hi Martin,

   Shouldn't/couldn't the ignore silently if excluded be 
 specified less
   strictly to cover the above permission denied error as well?
  
  I think you're right.  Martin Pool, what do you think?  
 Martin Bene, could
  you please try coding and testing a patch that will do what 
 you want?
 
 Yes, that sounds reasonable to me.

OK, I'll send a patch.

Bye, 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



Possible Bug report

2002-04-26 Thread Ferguson, Duncan

I have a server (A) with a directory structure I want to copy to another
server (/usr/local/bin...)
On the client (B), only /usr exists (/usr/local doesn't).

I used:
  /opt/PKGrsync/bin/rsync -a --delete --force
--rsync-path=/opt/PKGrsync/bin/rsync --exclude=save  -v -v /usr/local/bin
B:/usr/local/bin

but it failed with:
opening connection using /usr/bin/ssh B /opt/PKGrsync/bin/rsync --server
-vvlogDtpr --delete --force . /usr/local/bin 
building file list ... 
expand file_list to 4000 bytes, did move
excluding directory bin/save because of pattern save
done
rsync: mkdir /usr/local/bin: No such file or directory
rsync error: error in file IO (code 11) at main.c(285)
rsync: connection unexpectedly closed (8 bytes read so far)
rsync error: error in rsync protocol data stream (code 12) at io.c(150)

Creating /usr/local on B cured the problem and it worked without further
issue.  It seems the mkdir should include -p possibly.

Server (A) is on Solaris 2.6 5/98 105181-25
Client (B) is on Solaris 8 02/02 108528-13

Thanks

  Duncs

Duncan Ferguson
IT Infrastructure Senior Unix Systems Engineer

Phone: 01384 264 060
Mobile: 07968 148 748



This private and confidential e-mail has been sent to you by Egg.
The Egg group of companies includes Egg Banking plc
(registered no. 2999842), Egg Financial Products Ltd (registered
no. 3319027) and Egg Investments Ltd (registered no. 3403963) which
carries out investment business on behalf of Egg and is regulated
by the Financial Services Authority.  
Registered in England and Wales. Registered offices: 1 Waterhouse Square,
138-142 Holborn, London EC1N 2NA.
If you are not the intended recipient of this e-mail and have
received it in error, please notify the sender by replying with
'received in error' as the subject and then delete it from your
mailbox.


-- 
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: 4.4BSD chflags support for rsync

2002-04-26 Thread Dave Dykstra

On Fri, Apr 26, 2002 at 03:11:59AM +0200, Rolf Grossmann wrote:
 Hi Dave,
 
 on Thu, 25 Apr 2002 15:52:56 -0500 Dave Dykstra wrote 
 concerning Re: 4.4BSD chflags support for rsync something like this:
 
  I think the --flags patch is probably fine, except that that the short
  description should at least say preserve file flags instead of just
  preserve flags since most people wouldn't know what flags means.
 
 Sure, changed that (found 3 occurrences).
 
 However, I just recently found that I missed a case where I need to clear
 change flags: when (hard)linking to a file, that file may not have flags
 that prevent modification. Unfortunately, I didn't have time to look into
 that issue, yet.
 
 I also noticed, that you've been changing quite a few bits lately. E.g.
 there are rules to build texinfo documentation in the Makefile (but no
 texinfo files) and there is SGML documentation, but no rules for
 formatting. So I decided to wait some more before updating the patch
 to the current release (probably updating the new documentation then).
 So if you'd rather wait for me to update the patch (which is against 2.5.2),
 I'll probably get back to you either after the next release or in a
 week or two. Of course I'll be happy if you'll add the patch anyway ;)

Actually it will be up to the primary maintainer Martin Pool who has been
making those changes and it will be up to him to make the final decision on
if/when to put your patch in; I've just given my opinion as a former
primary maintainer.  Martin, what do you think?


  I don't like --ignore-existing, though.  What's the point of using rsync
  if you're not updating existing files?
 
 It's not my work. I was only saying that by building the manpage,
 the documentation for --ignore-existing also showed up. So unless it
 was explicitly removed for the release, it was simply forgotten to
 rebuild the manpage after the change.

Oops, sorry I didn't catch that.

- 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



Re: Handling of backup files - two new features proposed

2002-04-26 Thread Dave Dykstra

Why go through the trouble to nullify the --suffix option when --backup-dir
is specified?  I think it would be better to allow them to come in either
order anyway.

- Dave Dykstra

On Fri, Apr 26, 2002 at 01:52:24AM +0200, Michael Zimmermann wrote:
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1
 
 At Thursday 25 April 2002 23:47 Dave Dykstra wrote:
   [about proposing two new options]
--backup-owner=USER
--backup-group=GROUP
 
  I don't like that; I think it is too special purpose.  Can't you follow
  up the rsync with a find/chown?
 
 Yes, I agree. I was too fixed to the idea of preserving the user's
 quotas all the time.
 
 
   [about Adding a non-default suffix to backup-files in the backup-directory]
 
  That sounds like a fine idea to me.
 
 If you want to include it, I've added a patch against the current version -
 just as I would do the changes.
 
 
 Greetings
 Michael
 - -- 
 Michael Zimmermann (Vegaa Safety and Security for Internet Services)
 [EMAIL PROTECTED]   phone +49 89 6283 7632hotline +49 163 823 1195
 Key fingerprint = 1E47 7B99 A9D3 698D 7E35  9BB5 EF6B EEDB 696D 5811
 
 
 
 - --- snip ---
 diff -u rsync/backup.c rsync.dev/backup.c
 - --- rsync/backup.c  Fri Apr 26 00:51:18 2002
 +++ rsync.dev/backup.c  Fri Apr 26 01:03:39 2002
 @@ -203,12 +203,12 @@
 if (!file) return 1;
 
  /* make a complete pathname for backup file */
 - -if (strlen(backup_dir) + strlen(fname)  (MAXPATHLEN - 1)) {
 +if (strlen(backup_dir) + strlen(fname) + strlen(backup_suffix)  
(MAXPATHLEN - 1)) {
  rprintf (FERROR, keep_backup filename too long\n);
  return 0;
  }
 
 - -snprintf(keep_name, sizeof (keep_name), %s/%s, backup_dir, fname);
 +snprintf(keep_name, sizeof (keep_name), %s/%s%s, backup_dir, fname, 
backup_suffix);
 
 
  #ifdef HAVE_MKNOD
 diff -u rsync/options.c rsync.dev/options.c
 - --- rsync/options.c Fri Apr 26 00:52:15 2002
 +++ rsync.dev/options.c Fri Apr 26 01:37:09 2002
 @@ -361,7 +361,7 @@
{log-format,   0,  POPT_ARG_STRING, log_format , 0, 0, 0 },
{bwlimit,  0,  POPT_ARG_INT,bwlimit , 0, 0, 0 },
{address,  0,  POPT_ARG_STRING, bind_address, 0, 0, 0 },
 - -  {backup-dir,   0,  POPT_ARG_STRING, backup_dir , 0, 0, 0 },
 +  {backup-dir,   0,  POPT_ARG_STRING, backup_dir , OPT_BACKUP_DIR, 0, 0 },
{hard-links,  'H', POPT_ARG_NONE,   preserve_hard_links , 0, 0, 0 },
{read-batch,   0,  POPT_ARG_STRING, batch_prefix, OPT_READ_BATCH, 0, 0 },
{write-batch,  0,  POPT_ARG_STRING, batch_prefix, OPT_WRITE_BATCH, 0, 0 },
 @@ -470,6 +470,13 @@
  print_rsync_version(FINFO);
 exit_cleanup(0);
 
 +   case OPT_BACKUP_DIR:
 +   /* Using backup-directory nullifies
 +  a default backup-suffix */
 +   if (strcmp(backup_suffix,BACKUP_SUFFIX) == 0)
 +   backup_suffix = ;
 +   break;
 +
 case OPT_MODIFY_WINDOW:
  /* The value has already been set by popt, but
   * we need to remember that we're using a
 diff -u rsync/rsync.1 rsync.dev/rsync.1
 - --- rsync/rsync.1   Fri Apr 26 00:52:44 2002
 +++ rsync.dev/rsync.1   Fri Apr 26 01:45:56 2002
 @@ -428,11 +428,18 @@
  .IP \fB--backup-dir=DIR\fP
  In combination with the --backup option, this
  tells rsync to store all backups in the specified directory\. This is
 - -very useful for incremental backups\.
 +very useful for incremental backups\.  You can additionally
 +specify a backup suffix using the --suffix option
 +(otherwise the files backed up in the specified directory
 +will keep their original filenames)\. If the default suffix should
 +be used in this case, the --suffix=~ parameter must be given explicitly
 +after the --backup-dir parameter on the command line\.
  .IP
  .IP \fB--suffix=SUFFIX\fP
  This option allows you to override the default
  backup suffix used with the -b option\. The default is a ~\.
 +If --backup-dir and --suffix are both specified,
 +the SUFFIX is appended to the filename even in the backup directory.
  .IP
  .IP \fB-u, --update\fP
  This forces rsync to skip any files for which the
 - --- snip ---
 -BEGIN PGP SIGNATURE-
 Version: GnuPG v1.0.6 (GNU/Linux)
 Comment: For info see http://www.gnupg.org
 
 iD8DBQE8yJa472vu22ltWBERAvOIAJ9crT1Nt5qQWUJWMclVM2UVgghlqACfS/pK
 Ya55fnKf2sA9mBctC32IDHA=
 =c9MR
 -END PGP SIGNATURE-
 
 

-- 
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.5 - Utilizing exclude from in rsync.conf

2002-04-26 Thread Paul Slinski

I am attempting to utilize the exclude from option in my rsync configuration 
file (rather than maintain lists on users machines) but it does not appear to 
be working.

One example, I placed *.mp3 in the file to keep them from syncing mp3 files to 
the server and jamming up space. But rsync just seems to ignore this and 
syncs the files anyway without any errors to the syslog.

All of my configurations are in /etc

Here is rsyncd.conf
pid file = /var/run/rsyncd.pid
max connections = 2
use chroot = yes
motd file = /etc/rsyncd.motd
log file = /arch1/sync/rsync.log

[test]
path = /arch1/sync/paul
list = false
read only = false
uid = 900
gid = 900
exclude from = /etc/rsyncd.excludes
auth users = paul
secrets file = /etc/rsyncd.secrets
hosts allow = 192.168.10.10

-
And file permissions
-rw-r--r--1 root root  355 Apr 26 11:21 /etc/rsyncd.conf
-rw-r--r--1 root root  344 Apr 26 10:20 /etc/rsyncd.excludes
-rw-r--r--1 root root  242 Apr 26 10:36 /etc/rsyncd.motd
-rw---1 root root   14 Apr 26 10:34 /etc/rsyncd.secrets

I've looked around the web and archives for an answer, so now I turn to you.
Any suggestions are welcome.

-- 
Paul Slinski
System Administrator
Global IQX
http://www.globaliqx.com/
[EMAIL PROTECTED]


--
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: Handling of backup files - two new features proposed

2002-04-26 Thread Michael Zimmermann

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

At Friday 26 April 2002 16:02 Dave Dykstra wrote:
 Why go through the trouble to nullify the --suffix option when --backup-dir
 is specified?  I think it would be better to allow them to come in either
 order anyway.

The -suffix is initialized to ~. This was just my primitive way to avoid
code changes.

The other way around, an additional boolean like 'suffix_specified' might
come handy.

Michael
- --
Michael Zimmermann (Vegaa Safety and Security for Internet Services)
[EMAIL PROTECTED]   phone +49 89 6283 7632hotline +49 163 823 1195
Key fingerprint = 1E47 7B99 A9D3 698D 7E35  9BB5 EF6B EEDB 696D 5811

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD4DBQE8yX4572vu22ltWBERAh/CAKCDN6LuwPZ2hR9QT4aKR2FBApnL8ACYox1q
ToSZwbsvU3sq//RpIAY/9g==
=aJZE
-END PGP SIGNATURE-




-- 
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: Patch to avoid 'Connection reset by peer' error for rsync on cygwin

2002-04-26 Thread Max Bowsher

I though that shutdown acts as below:
--
Syntax:
int shutdown(int sockfd, int howto);
returns 0 if OK, -1 on error.

Action of the function depends on the value of howto -
SHUT_RD - read half of the connection is closed. The data currently in the
socket receive buffer is discarded.
SHUT_WR - write half of the connection is closed. The data in the socket send
buffer is sent followed by the normal TCP connection termination sequence.
SHUT_RDWR - both read and write halves of the connection are closed.
--
( from
http://www.google.com/search?q=cache:B6qVFvpm-p4C:www.ncst.ernet.in/~netfac/PGDI
T/ppt/IOmultiplex.ppt+Unix+socket+programming+shutdown+SHUT_WRhl=enie=UTF8)

SUSv2 is annoyingly somewhat vague on the specifics.

Perhaps you were thinking of SHUT_RD as discarding data? My patch used only
SHUT_WR, so it should be safe unless the above is totally wrong.

I've just done a quick test with my patch on Linux, and didn't see any problem.


Max.


Martin Pool [EMAIL PROTECTED] wrote:
 From memory, Practical TCP Programming says that this behaviour is
 caused by a misunderstanding of the sockets API by the WinSock
 programmers.  The correct meaning of shutdown() on Unix is to throw
 away any outstanding data and close the socket immediately.  Normally,
 when you close a socket, you do want to let any pending data get
 across, so it's rarely used.

 On Windows shutdown() does not throw away data, and should be called.
 (Trust M$ to get it backwards and force everybody else to adapt.)

 So the patch cannot go in as is, because I think it will break Unix.
 Something like it can go in, #ifdefed for W32.




smime.p7s
Description: application/pkcs7-signature


Re: Handling of backup files - two new features proposed

2002-04-26 Thread Dave Dykstra

On Fri, Apr 26, 2002 at 09:55:12AM +0200, Stefan Nehlsen wrote:
 On Thu, Apr 25, 2002 at 04:47:36PM -0500, Dave Dykstra wrote:
  On Mon, Apr 01, 2002 at 06:14:38PM +0200, Michael Zimmermann wrote:
   1.) Setting owner and/or group of backup files.
   
   In our servers I'm using rsync to backup to a hot standby machine.
   The users have access to this backup-server too, so that they
   can retrieve older versions of their files. At the same time the backup
   copies should not count in the user's quota (and/or should only
   be deletable by root or a special group-admin).
   
   To accomplish this, the backup files get their user and/or group set to
   a special user and/or group in our local version of rsync.
   
   Two new options control this behaviour
   
--backup-owner=USER
--backup-group=GROUP
  
  
  I don't like that; I think it is too special purpose.  Can't you follow
  up the rsync with a find/chown?
 
 no -- that would mess up timestamps

Only the inode change time, not the modification time.  The inode change
time is not copied exactly from any other time anyway so if it's a short
period of time later it shouldn't make any difference.


 But you are right there are too many options.

- Dave

-- 
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: rsync 2.5.5 - Utilizing exclude from in rsync.conf

2002-04-26 Thread Dave Dykstra

What's in rsyncd.excludes, and what's the command line.  A common problem
is that people don't know exactly which path components to include in
the exclude list.  Using -vv often helps with debugging excludes.

- Dave Dykstra


On Fri, Apr 26, 2002 at 11:26:38AM -0400, Paul Slinski wrote:
 I am attempting to utilize the exclude from option in my rsync configuration 
 file (rather than maintain lists on users machines) but it does not appear to 
 be working.
 
 One example, I placed *.mp3 in the file to keep them from syncing mp3 files to 
 the server and jamming up space. But rsync just seems to ignore this and 
 syncs the files anyway without any errors to the syslog.
 
 All of my configurations are in /etc
 
 Here is rsyncd.conf
 pid file = /var/run/rsyncd.pid
 max connections = 2
 use chroot = yes
 motd file = /etc/rsyncd.motd
 log file = /arch1/sync/rsync.log
 
 [test]
 path = /arch1/sync/paul
 list = false
 read only = false
 uid = 900
 gid = 900
 exclude from = /etc/rsyncd.excludes
 auth users = paul
 secrets file = /etc/rsyncd.secrets
 hosts allow = 192.168.10.10
 
 -
 And file permissions
 -rw-r--r--1 root root  355 Apr 26 11:21 /etc/rsyncd.conf
 -rw-r--r--1 root root  344 Apr 26 10:20 /etc/rsyncd.excludes
 -rw-r--r--1 root root  242 Apr 26 10:36 /etc/rsyncd.motd
 -rw---1 root root   14 Apr 26 10:34 /etc/rsyncd.secrets
 
 I've looked around the web and archives for an answer, so now I turn to you.
 Any suggestions are welcome.
 
 -- 
 Paul Slinski
 System Administrator
 Global IQX
 http://www.globaliqx.com/
 [EMAIL PROTECTED]

-- 
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: Patch to avoid 'Connection reset by peer' error for rsync on cygwin

2002-04-26 Thread Jos Backus

On Fri, Apr 26, 2002 at 05:40:07PM +0100, Max Bowsher wrote:
 Action of the function depends on the value of howto -
 SHUT_RD - read half of the connection is closed. The data currently in the
 socket receive buffer is discarded.
 SHUT_WR - write half of the connection is closed. The data in the socket send
 buffer is sent followed by the normal TCP connection termination sequence.
 SHUT_RDWR - both read and write halves of the connection are closed.

Slightly off-topic (sorry) but interesting perhaps: had socket() been designed
to return an int[2] (like pipe() and socketpair()), shutdown() would not have
been necessary and one could have just used close() on each descriptor
instead.

-- 
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



RE: Patch to avoid 'Connection reset by peer' error for rsync on cygwin

2002-04-26 Thread David Bolen

Max Bowsher [[EMAIL PROTECTED]] writes:

 I though that shutdown acts as below:
(no data loss)
 SUSv2 is annoyingly somewhat vague on the specifics.

So are the FreeBSD/Linux man pages.  They don't specifically indicate
truncation or flushing of data, although I don't recall ever thinking
of shutdown() as truncating.

To be, what Microsoft got wrong in WinSock is _requiring_ shutdown()
to reliably close a socket while ensuring all final data gets
delivered.  It certainly caught me by surprise (and annoyance) at one
point.  I rarely ever used it in a Unix environment, but I do think it
should be safe.

-- David

/---\
 \   David Bolen\   E-mail: [EMAIL PROTECTED]  /
  | FitLinxx, Inc.\  Phone: (203) 708-5192|
 /  860 Canal Street, Stamford, CT  06902   \  Fax: (203) 316-5150 \
\---/

-- 
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: error in rsync protocol data stream

2002-04-26 Thread Dave Dykstra

I know this is late but nobody else appears to have responded.

On Wed, Apr 03, 2002 at 11:43:48PM -0500, Scott Lipcon wrote:
 Hello,
 
 I'm having a problem doing a remote rsync over ssh -  i'm using a script that 
 has worked for quite a while, using rsync 2.4.6 on both ends.  I upgraded the 
 client to 2.5.5, and began seeing this error:
 
 rsync: connection unexpectedly closed (158246 bytes read so far)
 rsync error: error in rsync protocol data stream (code 12) at io.c(150)

This message occurs any time the remote end disappears early.


 At which time there is a large core file generated on the remote side 
 (unfortuantely, the debugger on the remote side isn't giving me anything 
 useful)
 
 I assumed that it was a bad interaction between the local 2.5.5 and the remote 
 2.4.6, so I upgraded the remote machine to 2.5.5 as well, and the problem 
 remains.  My local machine is an athlon running FreeBSD 4.5, and the remote 
 side is a Sparc 5 running OpenBSD 2.8.  The command line I'm using is:
 
 rsync -avz -P --delete --include-from=/u0/includes --partial remote:/ .
 
 I'd appreciate any ideas... please cc replies to me.
 
 Thanks,
 
 Scott


A crashing problem on FreeBSD has been found where the rsync zlib library 
crashes unless it is compiled with gcc -O2.  It sounds like it's your
Sparc OpenBSD side that's crashing though so I wouldn't think it would
be the same problem.  At least try it without -z.

- 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



Re: rsync 2.5.5 - Utilizing exclude from in rsync.conf

2002-04-26 Thread Paul Slinski

Is there a way to do debuging on the sever end? I've tried: rsync -vv --daemon 
--no-detach but I dont get any output.

The exclude contains to following (I'm sure this could be done differently):

#
# Common junk directories
#
/COOKIES
/Cookies
/cookies
/TEMPOR*
/Temporary*
#
# NTUSER.DAT does NOT like to be touched!
#
NTUSER.DAT
#
# Common junk files
#
*.tmp
*.slt
*.mp3
*.MP3
*.ogg
*.OGG
*.wma
*.mpg
*.MPG
*.mpeg
*.MPEG
*.avi
*.AVI
*.mov
*.MOV
*.mp2
#
# Misc crap files
#
Desktop.ini
desktop.ini
DESKTOP.INI

On April 26, 2002 12:44 pm, Dave Dykstra wrote:
 What's in rsyncd.excludes, and what's the command line.  A common problem
 is that people don't know exactly which path components to include in
 the exclude list.  Using -vv often helps with debugging excludes.

 - 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



Re: --bwlimit server-side (in rsyncd.conf)?

2002-04-26 Thread Dave Dykstra

On Thu, Apr 04, 2002 at 02:05:56PM +0200, Lapo Luchini wrote:
 Is there any plan to do it?
 Is it maybe already in and just not documented?


It's not currently there, and there's no plan to do it.  I expect a clean
patch to implement it would be accepted.

- 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



Re: rsync 2.5.5 - Utilizing exclude from in rsync.conf

2002-04-26 Thread Dave Dykstra

No, the -vv has to be on the client side.  The fact that most of your
patterns don't have a '/' in them makes them pretty simply and it seems
like they ought to work.  Excludes specified on the server can be overridden
by the client, however.  What is the command line on the client?  Do the
files get excluded if you specify it on the client side?  What version is
of rsync is running on both sides, and what are the operating systems?

- Dave Dykstra

On Fri, Apr 26, 2002 at 01:51:54PM -0400, Paul Slinski wrote:
 Is there a way to do debuging on the sever end? I've tried: rsync -vv --daemon
 --no-detach but I dont get any output.
 
 The exclude contains to following (I'm sure this could be done differently):
 
 #
 # Common junk directories
 #
 /COOKIES
 /Cookies
 /cookies
 /TEMPOR*
 /Temporary*
 #
 # NTUSER.DAT does NOT like to be touched!
 #
 NTUSER.DAT
 #
 # Common junk files
 #
 *.tmp
 *.slt
 *.mp3
 *.MP3
 *.ogg
 *.OGG
 *.wma
 *.mpg
 *.MPG
 *.mpeg
 *.MPEG
 *.avi
 *.AVI
 *.mov
 *.MOV
 *.mp2
 #
 # Misc crap files
 #
 Desktop.ini
 desktop.ini
 DESKTOP.INI
 
 On April 26, 2002 12:44 pm, Dave Dykstra wrote:
  What's in rsyncd.excludes, and what's the command line.  A common problem
  is that people don't know exactly which path components to include in
  the exclude list.  Using -vv often helps with debugging excludes.
 
  - 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



Re: rsync 2.5.5 - Utilizing exclude from in rsync.conf

2002-04-26 Thread Paul Slinski

Dave,

Excludes worked fine from client to server. Both systems are RedHat Linux 7.2 
(2.4.18 kernel) 

Rsync output on both systems (snipped):
rsync  version 2.5.5  protocol version 26
Capabilities: 64-bit files, socketpairs, hard links, symlinks, batchfiles,
IPv6, 64-bit system inums, 64-bit internal inums

Command line is
rsync -vv -a -z /home/paul/graphica/ [EMAIL PROTECTED]::test/

Maybe I need to use excludes on the clients instead.

On April 26, 2002 05:23 pm, Dave Dykstra wrote:
 No, the -vv has to be on the client side.  The fact that most of your
 patterns don't have a '/' in them makes them pretty simply and it seems
 like they ought to work.  Excludes specified on the server can be
 overridden by the client, however.  What is the command line on the client?
  Do the files get excluded if you specify it on the client side?  What
 version is of rsync is running on both sides, and what are the operating
 systems?

 - Dave Dykstra

-- 
Paul Slinski
System Administrator
Global IQX
http://www.globaliqx.com/
[EMAIL PROTECTED]


--
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: AIX issue using chroot

2002-04-26 Thread Dave Dykstra

On Wed, Apr 10, 2002 at 01:46:44AM -0400, Corey Stup wrote:
 Took a while to figure this one out:
 
 Since use chroot defaults to true, I was having issues of UID/GID's
 not mapping between servers.   On AIX, if chroot() is called, the
 getpwuid() calls fail, no longer being able to find /etc/passwd.   
 Since the that call doesn't differentiate between a 'failure' and a
 'unable to map uid', rsync assumes it can't map the UID and the server
 side doesn't send the maps.
 
 Setting use chroot to false is a workaround.   Not sure if there is an
 easy way to fix this, or its just a caveat that might want to be stated
 in the documentation.

That is the way it behaves on all operating systems.  It is mentioned in
the documentation, but not in a very easy to find place: under the
--numeric-ids option.  If you suggest a wording for a place in the man
pages that would be easy to find, we could put it in.


 Also, I would be happy to provide builds of rsync for AIX4.1.5 and
 4.3.3.

Martin, you could probably easily give volunteers write access to selected
binaries directories by making a password-protected module in
/etc/rsyncd.conf for them.  I don't see any in there now though so it would
be a new precedent.

- 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



Re: AIX issue using chroot

2002-04-26 Thread Martin Pool

On 26 Apr 2002, Dave Dykstra [EMAIL PROTECTED] wrote:

  Also, I would be happy to provide builds of rsync for AIX4.1.5 and
  4.3.3.
 
 Martin, you could probably easily give volunteers write access to selected
 binaries directories by making a password-protected module in
 /etc/rsyncd.conf for them.  I don't see any in there now though so it would
 be a new precedent.

I'll do that.

-- 
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