rsync listen to two TCP ports

2003-04-02 Thread addady
Hello,

I using red-had Linux 8.0 with two IP addresses.
On the first IP rsync is listen to port 873 and Apache web server to port
80.
What I need to do so that rsync will listen also to port 80 on the second IP
address ?

Thanks,
Addady

-- 
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: Solution For Rsync and Cygwin Daylight Savings Timezone Problems

2003-04-02 Thread Martin Sapsed
jw schultz wrote:
 [...]

The impact of this may be minimized by running rsync with
the --modify-window=3601 command-line option.  This will
cause rsync to ignore modification time differences of one
hour will allow rsync jobs to complete in the usual time
period with a minimal impact on backup integrity.  To get
back to normal it will be necessary to run rsync with the
usual modify-window on all files.  This can be done in
stages.
Am I right in thinking that if you use this option, files will still be 
selected for syncing if the checksums are different, even if the times 
are less than 3601 seconds apart?

Cheers,

Martin

--
Martin Sapsed   
Information Services   Who do you say I am?
University of Wales, Bangor Jesus of Nazareth
--
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: need to modify file data before storing it on destination

2003-04-02 Thread Kyle Jones
Here's a patch against rsync 2.5.6 that implements --dest-filter
(discussed as --remotefilter) and --times-only.  If anyone cares
to try it out and let me know if it works on your system, I'd
appreciate it.  I'll be distributing this patch with my snapshot
utilities.

*** rsync-2.5.6/generator.c Thu Aug 29 07:44:55 2002
--- rsync-2.5.6.patched/generator.c Tue Apr  1 11:18:49 2003
***
*** 35,40 
--- 35,42 
  extern int block_size;
  extern int csum_length;
  extern int ignore_times;
+ extern int times_only;
+ extern char *dest_filter;
  extern int size_only;
  extern int io_timeout;
  extern int remote_version;
***
*** 48,55 
  static int skip_file(char *fname,
 struct file_struct *file, STRUCT_STAT *st)
  {
!   if (st-st_size != file-length) {
!   return 0;
}
if (link_dest) {
if((st-st_mode  ~_S_IFMT) !=  (file-mode  ~_S_IFMT)) {
--- 50,59 
  static int skip_file(char *fname,
 struct file_struct *file, STRUCT_STAT *st)
  {
!   if (! times_only) {
!   if (st-st_size != file-length) {
!   return 0;
!   }
}
if (link_dest) {
if((st-st_mode  ~_S_IFMT) !=  (file-mode  ~_S_IFMT)) {
***
*** 58,63 
--- 62,70 
if (st-st_uid != file-uid || st-st_gid != file-gid) {
return 0;
}
+   }
+   if (times_only) {
+   return (cmp_modtime(st-st_mtime,file-modtime) == 0);
}
  

*** rsync-2.5.6/options.c   Mon Jan 27 19:11:57 2003
--- rsync-2.5.6.patched/options.c   Tue Apr  1 22:00:58 2003
***
*** 48,53 
--- 48,55 
  int dry_run=0;
  int local_server=0;
  int ignore_times=0;
+ char *dest_filter = NULL;
+ int times_only=0;
  int delete_mode=0;
  int delete_excluded=0;
  int one_file_system=0;
***
*** 207,212 
--- 209,215 
rprintf(F, -v, --verbose   increase verbosity\n);
rprintf(F, -q, --quiet decrease verbosity\n);
rprintf(F, -c, --checksum  always checksum\n);
+   rprintf(F, --dest-filter=COMMAND   filter file through COMMAND at 
destination\n);
rprintf(F, -a, --archive   archive mode, equivalent to -rlptgoD\n);
rprintf(F, -r, --recursive recurse into directories\n);
rprintf(F, -R, --relative  use relative path names\n);
***
*** 246,251 
--- 249,255 
rprintf(F, --timeout=TIME  set IO timeout in seconds\n);
rprintf(F, -I, --ignore-times  don't exclude files that match length and 
time\n);
rprintf(F, --size-only only use file size when determining if a 
file should be transferred\n);
+   rprintf(F, --times-only only use file modification time when 
determining if a file should be transferred\n);
rprintf(F, --modify-window=NUM Timestamp window (seconds) for file match 
(default=%d)\n,modify_window);
rprintf(F, -T  --temp-dir=DIR  create temporary files in directory 
DIR\n);
rprintf(F, --compare-dest=DIR  also compare destination files relative to 
DIR\n);
***
*** 283,288 
--- 287,293 
  }
  
  enum {OPT_VERSION = 1000, OPT_SUFFIX, OPT_SENDER, OPT_SERVER, OPT_EXCLUDE,
+   OPT_DEST_FILTER,
OPT_EXCLUDE_FROM, OPT_DELETE, OPT_DELETE_EXCLUDED, OPT_NUMERIC_IDS,
OPT_RSYNC_PATH, OPT_FORCE, OPT_TIMEOUT, OPT_DAEMON, OPT_CONFIG, OPT_PORT,
OPT_INCLUDE, OPT_INCLUDE_FROM, OPT_STATS, OPT_PARTIAL, OPT_PROGRESS,
***
*** 300,305 
--- 305,312 
{rsync-path,   0,  POPT_ARG_STRING, rsync_path,  0, 0, 0 },
{password-file,0,  POPT_ARG_STRING, password_file,   0, 0, 0 },
{ignore-times,'I', POPT_ARG_NONE,   ignore_times , 0, 0, 0 },
+   {times-only,   0,  POPT_ARG_NONE,   times_only , 0, 0, 0 },
+   {dest-filter,  0,  POPT_ARG_STRING, dest_filter , OPT_DEST_FILTER, 0, 0 },
{size-only,0,  POPT_ARG_NONE,   size_only , 0, 0, 0 },
{modify-window,0,  POPT_ARG_INT,modify_window, OPT_MODIFY_WINDOW, 0, 0 
},
{one-file-system, 'x', POPT_ARG_NONE,   one_file_system , 0, 0, 0 },
***
*** 471,476 
--- 478,488 
  print_rsync_version(FINFO);
exit_cleanup(0);

+   case OPT_DEST_FILTER:
+   /* dest_filter already set by popt */
+   whole_file = 1;
+   break;
+ 
case OPT_SUFFIX:
  /* The value has already been set by popt, but
   * we need to remember that a suffix was specified
***
*** 631,636 
--- 643,655 
return 0;
}
  
+   if (dest_filter  no_whole_file) {
+   

Re: Solution For Rsync and Cygwin Daylight Savings Timezone Problems

2003-04-02 Thread jw schultz
On Wed, Apr 02, 2003 at 03:33:30PM +0100, Martin Sapsed wrote:
 jw schultz wrote:
  [...]
 
 The impact of this may be minimized by running rsync with
 the --modify-window=3601 command-line option.  This will
 cause rsync to ignore modification time differences of one
 hour will allow rsync jobs to complete in the usual time
 period with a minimal impact on backup integrity.  To get
 back to normal it will be necessary to run rsync with the
 usual modify-window on all files.  This can be done in
 stages.
 
 Am I right in thinking that if you use this option, files will still be 
 selected for syncing if the checksums are different, even if the times 
 are less than 3601 seconds apart?

If they have the same length and you don't use the -c
option which will slow things considerably.
Rsync will not ignore changes in file size which
significantly reduces the sorts of file mods that would be
missed.

It takes a very unusual pattern to produce a wrongful skip.
This is the script of what it takes to do it.

modify file
rsync
modify file

These three steps must occur in sequence and all within one
hour and the file size must remain unchanged.

Any modifications of the file more than one hour after the
last modification prior to the last rsync will be outside the
3601 second modify-window and picked up by the next rsync.

I don't suggest making 3601 the normal modify-window.  I
only say that setting it to 3601 will allow the deferral of
fixing the mod-times.

Here is another possibility that just occurred to me for
correcting with the problem.  This will change the
timestamps of the files.  Whether you use a positive or
negative shift will depend on which end you decide to
adjust.

touch -d '01:00 13-apr-03' /tmp/cmpfile
find . -type f ! -newer /tmp/cmpfile | shifttime.pl 3600.

-- shifttime.pl ---
#!/usr/bin/perl

$offset = shift;

$offset += 0;

!$offset and die must give offset;

while (STDIN)
{
chomp;
-w or next;
$oldtime = (stat $_)[9];
$oldtime or next;
$newtime = $oldtime + $offset;
utime $newtime, $newtime, $_;
}



-- 

J.W. SchultzPegasystems Technologies
email address:  [EMAIL PROTECTED]

Remember Cernan and Schmitt
-- 
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: [Acl-Devel] mask ACL

2003-04-02 Thread Buck Huppmann
On Tue, Apr 01, 2003 at 11:09:32PM -0500, Buck Huppmann wrote:
 yes, my bad. sorry. before i throw out more babies with the bathwater,
 though, anybody know if any other systems besides HP-UX and Solaris
 (for default ACLs, at least) require a MASK/CLASS_OBJ when there are
 no non-USER_OBJ/GROUP_OBJ/OTHER entries?
 
 thanks, Eric C., for finding this out

to wind this up, for anybody who cares, the latest, greatest versions
of this patch are up at http://www.lpmd.org/rsync/ (thanks to John C.
again for hosting) for 2.5.5 and 2.5.6. use at your own risk, but let
me know if you find bugs (so i can mitigate my own risk)

on the matter of which platforms require masks/CLASS_OBJs, i gave the
samba sysacls.c a quick once over and discerned that, at least for
the mappings as implemented therein, HP-UX, Unixware and Solaris re-
quire CLASS_OBJs, which the new code synthesizes by or-ing all group
and named-user ACEs, as you might expect, in the absence of a source
mask/CLASS_OBJ entry
-- 
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: [Acl-Devel] mask ACL

2003-04-02 Thread Andreas Gruenbacher
On Thursday 03 April 2003 05:26, Buck Huppmann wrote:
 On Tue, Apr 01, 2003 at 11:09:32PM -0500, Buck Huppmann wrote:
  yes, my bad. sorry. before i throw out more babies with the bathwater,
  though, anybody know if any other systems besides HP-UX and Solaris
  (for default ACLs, at least) require a MASK/CLASS_OBJ when there are
  no non-USER_OBJ/GROUP_OBJ/OTHER entries?
 
  thanks, Eric C., for finding this out

 to wind this up, for anybody who cares, the latest, greatest versions
 of this patch are up at http://www.lpmd.org/rsync/ (thanks to John C.
 again for hosting) for 2.5.5 and 2.5.6. use at your own risk, but let
 me know if you find bugs (so i can mitigate my own risk)

 on the matter of which platforms require masks/CLASS_OBJs, i gave the
 samba sysacls.c a quick once over and discerned that, at least for
 the mappings as implemented therein, HP-UX, Unixware and Solaris re-
 quire CLASS_OBJs, which the new code synthesizes by or-ing all group
 and named-user ACEs, as you might expect, in the absence of a source
 mask/CLASS_OBJ entry

You should also throw away CLASS_OBJs on those systems which require 
four-entry ACLs, possibly only the CLASS_OBJ entry's permissions are 
identical with the GROUP_OBJ permissions. If you don't do, all the files will 
get extended ACLs on the remote side. On those systems which require the 
CLASS_OBJs, the CLASS_OBJs are actually meaningless in the four-entry ACL 
case, anyway.

ACLs are a nice disaster.

Cheers,
Andreas.

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