similar to: [PATCH] (Resubmission) 'Connection reset by peer' with rsync server on cygwin

Displaying 20 results from an estimated 200 matches similar to: "[PATCH] (Resubmission) 'Connection reset by peer' with rsync server on cygwin"

2002 Apr 03
4
Patch to avoid 'Connection reset by peer' error for rsync on cygwin
The problem is caused because rsync does not close its sockets, and WinSock is a quite strict on this. The solution is to shutdown and close the fd. This is a 5-minute hack I've done to fix the obvious occurrences of the problem. It might be better to extend rsyncs cleanup functions for this, but here it is anyway to alert people to the problem and its fix. Max. BEGIN PATCH diff -mru
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 Jan 26
1
patch for linux capabilities
I was wondering if it might be possible for an rsync developer to look over the attached patch (tested on Linux 2.4.24 against the rsync-2.6.0 release), and offer suggestions on how I could improve it. Basically I want to use Linux finer grained capabilities to retain only CAP_SYS_CHROOT & CAP_DAC_READ_SEARCH when rsync drops root privs. That way I can take whole system backups as a (mostly)
2015 Feb 05
2
Resubmission after N days
> What specific action shall be done via IMAP? The move? > Then use any IMAP client library, use the LIST command to get the mailboxes, FETCH to get the messages and COPY/EXPUNGE > to move them. You are right moving the mail should be simple. I ask myself it is possible to store the date of the resubmission in the mail itself. Thomas
2015 Feb 06
0
Resubmission after N days
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thu, 5 Feb 2015, Thomas G?ttler wrote: > Am 05.02.2015 um 12:18 schrieb Steffen Kaiser: >> On Thu, 5 Feb 2015, Thomas G?ttler wrote: >>>> What specific action shall be done via IMAP? The move? >>>> Then use any IMAP client library, use the LIST command to get the mailboxes, FETCH to get the messages and COPY/EXPUNGE
2015 Feb 05
0
Resubmission after N days
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thu, 5 Feb 2015, Thomas G?ttler wrote: >> What specific action shall be done via IMAP? The move? >> Then use any IMAP client library, use the LIST command to get the >> mailboxes, FETCH to get the messages and COPY/EXPUNGE >> to move them. > > You are right moving the mail should be simple. > > I ask myself it
2015 Feb 04
0
Resubmission after N days
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed, 4 Feb 2015, Thomas G?ttler wrote: > I would like to implement a 43Folder system[1] with dovecot and a mail user agent. > > Use case: > > - I have a new mail in my inbox. I read it and see that I can't handle it now. I want to handle this mail in 5 days. > - Now I want to have some sort of resubmission: the mail should be
2015 Feb 04
0
AW: Resubmission after N days
Hi, Sounds to me like it can be implemented using sieve. Something like "if is in inbox & is read & is older than n days; then mark as unread". But this means you need to redeliever this mail somehow. Maybe like this: http://serverfault.com/questions/418681/run-sieve-on-maildir (http://serverfault.com/questions/418681/run-sieve-on-maildir) Regards Andr? Am Mi., Febr. 4, 2015
2015 Feb 05
0
Resubmission after N days
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed, 4 Feb 2015, Thomas G?ttler wrote: > Am 04.02.2015 um 07:49 schrieb Steffen Kaiser: >> On Wed, 4 Feb 2015, Thomas G?ttler wrote: >> >>> I would like to implement a 43Folder system[1] with dovecot and a mail user agent. >> >>> Use case: >> >>> - I have a new mail in my inbox. I read it and
2015 Feb 04
3
Resubmission after N days
Am 04.02.2015 um 07:49 schrieb Steffen Kaiser: > On Wed, 4 Feb 2015, Thomas G?ttler wrote: > >> I would like to implement a 43Folder system[1] with dovecot and a mail user agent. > >> Use case: > >> - I have a new mail in my inbox. I read it and see that I can't handle it now. I want to handle this mail in 5 days. >> - Now I want to have some sort of
2015 Feb 05
3
Resubmission after N days
Am 05.02.2015 um 12:18 schrieb Steffen Kaiser: > On Thu, 5 Feb 2015, Thomas G?ttler wrote: >>> What specific action shall be done via IMAP? The move? >>> Then use any IMAP client library, use the LIST command to get the mailboxes, FETCH to get the messages and COPY/EXPUNGE >>> to move them. > >> You are right moving the mail should be simple. > >>
2004 Feb 04
0
RAID 0 Problems - resubmission as subsriber
Can some one help me with a ext3 file sys problem?? I have a raid 0 array that was not shut down properly due to bad contacts in a removable drive bay. It consists of two 80Gb drives. I can create /dev/md0 ok. but if fails during mount. When I run: fsck -n /dev/md0 it reports the following: fsck 1.32 e2fsck 1.32 SuperBlock has a bad ext3 journal (inode 8) clear? no fsck.ext2: illegal inode
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:
2015 Feb 04
8
Resubmission after N days
Hi, I would like to implement a 43Folder system[1] with dovecot and a mail user agent. Use case: - I have a new mail in my inbox. I read it and see that I can't handle it now. I want to handle this mail in 5 days. - Now I want to have some sort of resubmission: the mail should be moved to a different location for these 5 days. - After 5 days the mail should be moved to my inbox again. How
2015 Apr 21
1
[Bug 11229] New: off-by-one in snprintf() check
https://bugzilla.samba.org/show_bug.cgi?id=11229 Bug ID: 11229 Summary: off-by-one in snprintf() check Product: rsync Version: 3.1.1 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 Component: core Assignee: wayned at samba.org Reporter: sbehrens at
2001 Aug 22
1
@RSYNC EXIT / @RSYNC EOF
tridge and Wayne in particular: I checked in this patch, which is meant to consolidate the ones from both of you for handling EOF in a modules list. The idea is that we need to handle servers that just close the socket rather than sending a nice ending token, but we want to keep EOF detection on in general. (The IO code is such a mess!) -- Martin Index: clientserver.c
2003 Feb 22
1
rsync ported to BeOS-bone
Hello, here is a preliminary patch allowing rsync 2.5.6 to compile in BeOS (using the new BONE networking stack). Some explanations: - BeOS doesn't have chroot(), - the BONE networking stack export legacy network function for old apps in libnet.so (linked to by default), so it's necessary to force linking to the new libraries for things to work. I've yet to get inet_ntop() to be
2003 Mar 11
0
PATCH: rsyncd.conf permission options
This is a patch to control unix permissions when uploading to a rsyncd-server by setting rsyncd.conf options. cu, Stefan -- Stefan Nehlsen | ParlaNet Administration | sn@parlanet.de | +49 431 988-1260 -------------- next part -------------- diff -ur rsync-2.5.5/loadparm.c rsync-2.5.5-umask/loadparm.c --- rsync-2.5.5/loadparm.c Mon Mar 25 05:04:23 2002 +++ rsync-2.5.5-umask/loadparm.c Sun Mar 2
2003 Jun 07
1
patch to rsync to add options for pre- and post-transfer commands
In case others find this of value, I wrote a patch to rsync 2.5.6 to give rsync in --daemon mode the ability to run a pre-transfer and post-transfer command. These options handle our need to prepare a server to receive files and to do some processing after receiving files. The options for /etc/rsyncd.conf are pretransfer script = /some/command/to/run posttransfer script =
2012 Mar 25
3
attempt to access beyond end of device and livelock
Hi Dongyang, Yan, When testing BTRFS with RAID 0 metadata on linux-3.3, we see discard ranges exceeding the end of the block device [1], potentially causing dataloss; when this occurs, filesystem writeback becomes catatonic due to continual resubmission. The reproducer is quite simple [2]. Hope this proves useful... Thanks, Daniel --- [1] attempt to access beyond end of device ram0: rw=129,