#1978 Rsync doesn't work as expected

[Ruben]

Hi,
I am running a script that is calling several unix commands, wich are working using MKS for windows but not rsync.
So I downloaded MINGW32 because of that but when I try to run it from my windows command prompt or from the bash prompt I am always getting this error.

C:\MinGW\msys\1.0\bin\sh.exe: *** fork: can't reserve memory for stack 0x4A0000

- 0x6A0000, Win32 error 0
6030086 [main] sh 1480 sync_with_child: child 2544(0x2A4) died before initializa
tion with status code 0x1
6030922 [main] sh 1480 sync_with_child: *** child state waiting for longjmp

The only command prompt that works is the one included in the program (MINGW32), but if I use this one, my pscp or sh commands don't work.
Is this a known issue due to a configuration error?
I was wondering if is there any way to call this prompt from a script sending a command so I can run my script in the windows command prompt. The rsync version is 3.0.8.

Regards,

Ruben

[Keith Marshall]

You'll need to give us much more detail of what you are trying to do, and how you are trying to do it. On the basis of what you've told us so far, all I can say is that msys-rsync v3.0.8 WJFFM.

[Earnie Boyd]

• Description has changed:

Diff:

--- old
+++ new
@@ -1,12 +1,14 @@
 Hi, 
 I am running a script that is calling several unix commands, wich are working using MKS for windows but not rsync.
 So I downloaded MINGW32 because of that but when I try to run it from my windows command prompt or from the bash prompt I am always getting this error.

- 
+
+~~~~~
 C:\MinGW\msys\1.0\bin\sh.exe: *** fork: can't reserve memory for stack 0x4A0000
 - 0x6A0000, Win32 error 0
 6030086 [main] sh 1480 sync_with_child: child 2544(0x2A4) died before initializa
 tion with status code 0x1
 6030922 [main] sh 1480 sync_with_child: *** child state waiting for longjmp
+~~~~~

 The only command prompt that works is the one included in the program (MINGW32), but if I use this one, my pscp or sh commands don't work. 
 Is this a known issue due to a configuration error?

• status: unread --> open
• Type: Bug --> Support

[Earnie Boyd]

The usual fix for these fork errors is to rebase the MSYS-1.0.DLL to a lower address space. Search for rebase msys using Google. If that doesn't help then you'll need to provide more information.

[Keith Marshall]

The more common scenario, in which a rebase is recommended, is when fork complains that it cannot reserve space for cygwin's heap. In this case, it's stack space which seems to be in short supply; nonetheless, a rebase may be worth a try.

The principal reason I asked for more info is: there's a hint in the OP's report that rsync may work correctly when run from an MSYS shell, (in MinGW32 personality), which is started in accordance with the normal MSYS.bat procedure. This being the case, and the problems arise when he enters definitively unsupported territory, (by trying to run rsync directly from a CMD.exe shell, or by otherwise bypassing the regular MSYS shell initialisation procedure), he may just be out of luck with an unsupported use-case which simply doesn't work.

I'm also curious as to why, if his scripts are in well formed Bourne shell syntax, they wouldn't run under MSYS shell? After all, these are precisely the sort of scripts that this shell should be ideal for running.