similar to: code 23 error.

Displaying 20 results from an estimated 300 matches similar to: "code 23 error."

2004 May 29
1
[patch] Filename conversion
Hi, One feature missing from rsync, and requested on this list before, is on-the-fly conversion of filename character encoding. For example, I often need to sync files having Hebrew filenames from a UTF-8 system (Linux) to an ISO8859-8 system (Cygwin on Windows 2000 using the non-Unicode Win32 interface). Other circumstances surely abound. Attached is a patch against rsync 2.6.2 that adds an
2004 Feb 12
1
[PATCH] write only
We use rsync to provide an rsync share on a linux server with a javascript program on Windows clients which ensures all client data is backed up each morning. After making no progress with my posting last month regarding making a module upload only to prevent someone from manually downloading the rsync share obtaining other users work (exclude = * wasn't possible because we need --delete to
2004 Jul 12
2
[PATCH] Batch-mode rewrite
Wayne, Please consider the attached patch. This applies to the current CVS, and is independant of patches/local-batch.diff. As a matter of fact, I'm sure it would conflict heavily with local-batch.diff. This version of batch mode has a couple distinguishing features: Write-batch records (almost) the entire sender side of the conversation into one file. ("Almost" because it has
2002 Feb 24
2
Write-only option
Hi! I am doing backups from a number of machines to an rsync server. For some time I was trying to come up with a solution, which would prevent users from peeking at each other's files, which are backed up. Finally, I've hacked rsync, introducing a new option "write only" for rsyncd.conf. When set to true, this option forbids the transfers from server to the client, thus solving
2001 Nov 20
2
rsync server over SSH [includes code patches]
Hi Folks -- I've recently had the need to add a piece of functionality to rsync that allows one to run 'rsync --daemon' (rsync in "rsync server" mode) over SSH. My main goal was to be able to use some of the features from rsyncd.conf(5) (notably modules) while still using SSH for authentication and network transport. Background: I wanted to have the capability of setting
2004 Jun 17
1
[PATCH] make write_batch local
Wayne, It's taken a little while for me to get more familiar with the code, but I think I've reached a good breakpoint in improving batch-mode. Let me highlight some of the changes in the attached patch: * --write-batch and --read-batch arguments are no longer passed from client to server. This fixes the current problem that causes the server threads to die when the client
2004 Jan 17
1
--delete-sent-files (AKA --move-files)
Yes, it's time once again to return to the subject of moving files. With the recent changes to the communications code between the receiver and the generator, there is now a non-clogging channel that we can use to signal the sender when a file has been successfully transferred, which allows us delete the original for all transferred files. I have in the past waffled on whether this feature
2004 Sep 28
1
[Patch] rsync-2.6.2: Allow 'port = N' in rsyncd.conf
Hi, If anyone is interested, the included patch to rsync-2.6.2 allows you to specify the port number for an rsync server as a global option in rsyncd.conf with 'port = <N>' (where <N> is your favorite port number). Note that this parameter only takes effect when the server is started, not when clients connect. Also, specifying the port in rsyncd.conf takes precedence
2003 Nov 17
0
[PATCH] --source-filter && --dest-filter for rsync 2.5.6
Hi, I needed to filter content of files (encrypt), before they are sent over the network to backup server. The easiest way to do this was modifying Kyle Jones's "--dest-filter" patch. Somebody was asking there this feature in the past, so I'm sending this patch to list. Implementation details: -filtering disables rsync alogrithm -source filter makes temporary files in /tmp
2023 Jul 03
0
[PATCH] Add option --log-after to log after moving file into place
This mode is useful when a process is monitoring the log for post-processing of transferred files. With --log-after in local mode, both sender and receiver log to the same log file, so it require --log-file with absolute path. We add %o to the default log format, so it will be easy to tell the logs of the sender from the logs of the receiver: 2023/02/14 14:40:25 [559755] building file list
2002 Jul 20
0
[PATCH] (Resubmission) Enable push to remote rsynced server using rsync:// URL
Hello, Recently I noticed a disparity in the use of HOST::MODULE and rsync://HOST/MODULE syntax by rsync. HOST::MODULE can be used to both pull from and push to a remote rsyncd server, but rsync://HOST/MODULE can only be used to pull from a remote rsyncd server. The attached patch resolves this issue by also allowing a rsync:// URL to be used to push files to a remote rsyncd server. Testing:
2004 Apr 22
2
[PATCH] --timelimit and --stopat
Greetings, Upon a suggestion to improve the --timelimit patch, I have also added a --stopat option. You can get the patch from this URL and/or cut/paste it from below. http://www.terry.uga.edu/~jft/rsync-timelimit-stopat.patch.gz Here are the details... --timelimit=T This option allows you to specify the maximum number of minutes rsync will run for. This time starts when
2003 Jul 24
0
(no subject)
Here is a diff which should allow applying batch updates remotely ( as apposed to copying the batch files to the remote server and running rsync there ). Eg rsync --write-batch=test src dst1::dst rsync --read-batch=test dst2::dst Oli Dewdney diff -E -B -c -r rsync-2.5.6/flist.c rsync-2.5.6-remotebatch/flist.c *** rsync-2.5.6/flist.c Sat Jan 18 18:00:23 2003 ---
2013 Oct 25
1
[PATCH] rsync-patches/slp.diff: use lp_num_modules instead of the removed lp_numserv
Hello, rsync-patches/slp.diff is still using lp_numserv which was removed by commit b583594ac7d2f8a38aca85c1bfa4b1487122377a Signed-off-by: Vitezslav Cizek <vcizek at suse.cz> --- slp.diff | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/slp.diff b/slp.diff index a9703f1..953b400 100644 --- a/slp.diff +++ b/slp.diff @@ -479,7 +479,7 @@ new file mode 100644 +
2002 Feb 07
1
Latest version of the batch mode cleanup patch
Here's the latest version of the batch mode cleanup patch. Index: batch.c =================================================================== RCS file: /cvsroot/rsync/batch.c,v retrieving revision 1.12 diff -u -r1.12 batch.c --- batch.c 24 Jan 2002 08:09:46 -0000 1.12 +++ batch.c 6 Feb 2002 19:47:57 -0000 @@ -8,55 +8,38 @@ #include "rsync.h" #include <time.h> -char
2004 Jan 25
2
scan for first existing hard-link file
Here's a patch that makes rsync try to find an existing file in a group of hard-linked files so that it doesn't create the first one in the group from scratch if a later file could be used instead. Details: I decided to avoid having the code do an extra scan down the list when we encounter the lead file in the list. This is because it would be bad to have to do the same scan in the
2003 Jan 14
4
specifying a list of files to transfer
Hi, I don't want to start another --files-from war, but I am attaching an updated version of my patch to allow you to specify a list of files to transfer. The normal rsync syntax allows you to specify a list of SRC files to transfer on the command line. This patch adds some new options to allow you to instead supply a file that contains a list of files to transfer. The previous version of
2005 Jan 31
1
[patch] add "--ignore" option
Hi, The patch below adds a "--ignore" option to rsync, which means "--exclude-but-dont-delete-even-if-we-specified--delete-excluded". I need this for a few tasks, the simplest of which is to have rsync resist trying to delete NetApp filers' ".snapshot" directories. The change is fairly simple (the boolean filter returns become tri-state), and works for me both
2004 Jan 27
1
Differentiating debug messages from both sides
Some of the debug messages that rsync outputs (when verbose >= 2) can occur on both sides of the connection. This makes it hard to know which program is saying what. Some debug messages deal with this by outputting a "[PID]" string at the start of the message. Unfortunately, the startup message that tells us which pid is which is only output when verbose >= 3, so there's a
2003 May 20
0
patch for better handling of write failures (disk full)
I've been having problems trying to sync two small partitions (128MB) that may be near to full. If rsync gets a write error (such as is caused when you fill up a partition) during a sync without the use of "-T", it will stop with this error: rsync: writefd_unbuffered failed to write 4 bytes: phase "unknown": Broken pipe rsync error: error in rsync protocol data stream