Re: Windows 8 Release Preview. fork problems with rsync

2012-06-21 Thread Larry Hall (Cygwin)
On 6/21/2012 9:30 AM, Assaf wrote: Hi, I'm also experiencing the following error on a Windows 2012 I can't get my Python paramiko SSHClient to connect and execute remote commands Sometimes its ok, sometimes it requires me to restart the connection From ssh log: 10349 [main] sshd 732 ope

Re: Windows 8 Release Preview. fork problems with rsync

2012-06-21 Thread Assaf
Hi, I'm also experiencing the following error on a Windows 2012 I can't get my Python paramiko SSHClient to connect and execute remote commands Sometimes its ok, sometimes it requires me to restart the connection From ssh log:   10349 [main] sshd 732 open_stackdumpfile: Dumping stack trace to

Re: Windows 8 Release Preview. fork problems with rsync

2012-06-18 Thread Corinna Vinschen
On Jun 7 10:35, Ryan Johnson wrote: > On 06/06/2012 12:12 PM, Corinna Vinschen wrote: > >On Jun 6 16:41, Bertrand Latinville wrote: > >>I'm using > >> > >> rsync --chmod=ug=rwX -arvz --prune-empty-dirs --include="*/" > >>--include-from=include-file.txt --exclude="*" ${source_dir}/ > >>${dest_d

Re: Windows 8 Release Preview. fork problems with rsync

2012-06-18 Thread Corinna Vinschen
On Jun 7 10:12, Noel Grandin wrote: > > > On 2012-06-06 20:29, Corinna Vinschen wrote: > > >On Jun 6 17:59, Nick Lowe wrote: > >>>Thanks. I can confirm the effect. For no apparent reason, the OS > >>>reserves a 1 Megs shared memory region, top-down allocated, of which it > >>>uses about 20K.

Re: Windows 8 Release Preview. fork problems with rsync

2012-06-07 Thread Ryan Johnson
On 06/06/2012 12:12 PM, Corinna Vinschen wrote: On Jun 6 16:41, Bertrand Latinville wrote: I'm using rsync --chmod=ug=rwX -arvz --prune-empty-dirs --include="*/" --include-from=include-file.txt --exclude="*" ${source_dir}/ ${dest_dir} Thanks. I can confirm the effect. For no apparent re

Re: Windows 8 Release Preview. fork problems with rsync

2012-06-07 Thread Noel Grandin
On 2012-06-06 20:29, Corinna Vinschen wrote: On Jun 6 17:59, Nick Lowe wrote: Thanks. I can confirm the effect. For no apparent reason, the OS reserves a 1 Megs shared memory region, top-down allocated, of which it uses about 20K. It's not the PEB or one of the TEBs, though. Nor is it a

Re: Windows 8 Release Preview. fork problems with rsync

2012-06-06 Thread Corinna Vinschen
Please, don't http://cygwin.com/acronyms/#TOFU Thank you. On Jun 6 17:59, Nick Lowe wrote: > > Thanks.  I can confirm the effect.  For no apparent reason, the OS > > reserves a 1 Megs shared memory region, top-down allocated, of which it > > uses about 20K.  It's not the PEB or one of the TEBs,

Re: Windows 8 Release Preview. fork problems with rsync

2012-06-06 Thread Nick Lowe
Urgh! Hmm.. Do you see the same effect when running the process in question under the Windows 8 operating system context? If you manifest and include: http://msdn.microsoft.com/en-us/library/windows/desktop/hh848036(v=vs.85).aspx Does the odd behaviour still pers

Re: Windows 8 Release Preview. fork problems with rsync

2012-06-06 Thread Corinna Vinschen
On Jun 6 16:41, Bertrand Latinville wrote: > I'm using > > rsync --chmod=ug=rwX -arvz --prune-empty-dirs --include="*/" > --include-from=include-file.txt --exclude="*" ${source_dir}/ > ${dest_dir} Thanks. I can confirm the effect. For no apparent reason, the OS reserves a 1 Megs shared memo

Re: Windows 8 Release Preview. fork problems with rsync

2012-06-06 Thread Bertrand Latinville
I'm using rsync --chmod=ug=rwX -arvz --prune-empty-dirs --include="*/" --include-from=include-file.txt --exclude="*" ${source_dir}/ ${dest_dir} The include list from include-file.txt is up to four lines with some wildcard like folder1/folder2/*.dll folder3/** 2012/6/6 Corinna Vinschen > On J

Re: Windows 8 Release Preview. fork problems with rsync

2012-06-06 Thread Corinna Vinschen
On Jun 6 12:57, Bertrand Latinville wrote: > Hello, > > I'm using cygwin 1.7.75 on Windows 8 Release Preview 64 bits. > Bash scripts are launched via jenkins. > > I'm getting some problems with rsync giving fork errors. > This is not systematic,this happens once over 6 times. > > building file