Re: git-svn: perl child_copy: linked dll data write copy failed

quot;git init" works, as does "git status" and "git svn help". But "git > >> svn init" spews (slowly) > >> > >> $ git svn init > >> 4 [main] perl 5624 child_copy: linked dll data write copy failed, > >> 0x6FE

Re: git-svn: perl child_copy: linked dll data write copy failed

lp". But "git >> svn init" spews (slowly) >> >> $ git svn init >> 4 [main] perl 5624 child_copy: linked dll data write copy failed, >> 0x6FEB60 >> 00..0x6FEB6080, done 0, windows pid 5624, Win32 error 487 > > I maintain git, but have no

Re: git-svn: perl child_copy: linked dll data write copy failed

t svn help". But "git > svn init" spews (slowly) > > $ git svn init > 4 [main] perl 5624 child_copy: linked dll data write copy failed, > 0x6FEB60 > 00..0x6FEB6080, done 0, windows pid 5624, Win32 error 487 I maintain git, but have no experience with git-svn (as

Re: git-svn: perl child_copy: linked dll data write copy failed

On Fri, Oct 31, 2008 at 07:55:48AM -0700, George Reilly wrote: >2008/10/31 Christopher Faylor <[EMAIL PROTECTED]>: >...I've just double checked my Trash and Spam folders in Gmail, and I >can find no bounces from the list. And I unwittingly sent two HTML >mails to the list before guessing what had

Re: git-svn: perl child_copy: linked dll data write copy failed

2008/10/31 Christopher Faylor <[EMAIL PROTECTED]>: > On Thu, Oct 30, 2008 at 10:07:19PM -0700, George Reilly wrote: >>Resending. I think the earlier copy failed to get through because it >>was HTML. It'd be nice if the mailing list software sent a rejection >>notice instead of silently dropping HTM

Re: git-svn: perl child_copy: linked dll data write copy failed

On Thu, Oct 30, 2008 at 10:07:19PM -0700, George Reilly wrote: >Resending. I think the earlier copy failed to get through because it >was HTML. It'd be nice if the mailing list software sent a rejection >notice instead of silently dropping HTML mail on the floor. The mailing list software does sen

git-svn: perl child_copy: linked dll data write copy failed

2008/10/30 Subject: git-svn: perl child_copy: linked dll data write copy failed To: Cygwin I installed Cygwin from scratch today on my Vista SP1 box, using the v2.573.2.3 setup.exe. I ran "ash rebaseall -v", which worked once I renamed cyglsa64.dll to a different extension. "git

Re: 1.5.21-1: sshd: "child_copy: linked dll data write copy failed" after computer reboot (Windows 2000 SP4)

Dan Harkless wrote: I wanted to follow up to the below thread from 2006 because I came across another situation that had the same symptoms but a different solution. More info below the old post. On November 8, 2006, Larry Hall (Cygwin) wrote: Dan Harkless wrote: On November 7, 2006, "Larry Ha

RE: 1.5.21-1: sshd: "child_copy: linked dll data write copy failed" after computer reboot (Windows 2000 SP4)

Dan Harkless wrote on 17 September 2008 18:42: > I wanted to follow up to the below thread from 2006 because [ ... ] A lot has happened since 2006! > [ ... ] McAfee [ ... ] In particular, we have created the http://cygwin.com/acronyms/#BLODA, on which (http://tinyurl.com/BLODA) you will see

Re: 1.5.21-1: sshd: "child_copy: linked dll data write copy failed" after computer reboot (Windows 2000 SP4)

I wanted to follow up to the below thread from 2006 because I came across another situation that had the same symptoms but a different solution. More info below the old post. On November 8, 2006, Larry Hall (Cygwin) wrote: > Dan Harkless wrote: > > On November 7, 2006, "Larry Hall (Cygwin)" wrot

Re: child_copy: linked dll data write copy failed

I'd like to know how you determined that a DLL was loaded with every process. I'm having the same problem, but I don't know how to debug it. I had some time to debug this, and found that it was the "Logitech Process Monitor" service, which I had recently installed (and forgotten about). It ap

Re: 1.5.21-1: sshd: "child_copy: linked dll data write copy failed" after computer reboot (Windows 2000 SP4)

On November 8, 2006, Christopher Faylor wrote: > On Wed, Nov 08, 2006 at 11:00:44AM -0800, Dan Harkless wrote: > >On November 8, 2006, Christopher Faylor wrote: > >>On Tue, Nov 07, 2006 at 11:03:30PM -0800, Dan Harkless wrote: > >>>I would suggest having the Cygwin webmaster update > >>>

Re: 1.5.21-1: sshd: "child_copy: linked dll data write copy failed" after computer reboot (Windows 2000 SP4)

Dan Harkless wrote: On November 7, 2006, "Larry Hall (Cygwin)" wrote: No. Another application using a different cygwin1.dll would have to be running. As long as it is, the old cygwin1.dll is loaded in memory and will cause conflicts. Kill'em. Okay. Good to know. Would the other copy need

Re: 1.5.21-1: sshd: "child_copy: linked dll data write copy failed" after computer reboot (Windows 2000 SP4)

On Wed, Nov 08, 2006 at 11:00:44AM -0800, Dan Harkless wrote: >On November 8, 2006, Christopher Faylor <[EMAIL PROTECTED]> wrote: >>On Tue, Nov 07, 2006 at 11:03:30PM -0800, Dan Harkless wrote: >>>I would suggest having the Cygwin webmaster update >>> to make the PCYMT

Re: 1.5.21-1: sshd: "child_copy: linked dll data write copy failed" after computer reboot (Windows 2000 SP4)

And after all that I forgot to manually strip the email address from the attribution line on that last mail (luckily it appears to be a fictional, pre-munged address): On November 8, 2006, Dan Harkless wrote: > On November 8, 2006, Christopher Faylor <[EMAIL PROTECTED]> wrote: The thing is, I'm

Re: 1.5.21-1: sshd: "child_copy: linked dll data write copy failed" after computer reboot (Windows 2000 SP4)

On November 8, 2006, Christopher Faylor <[EMAIL PROTECTED]> wrote: > On Tue, Nov 07, 2006 at 11:03:30PM -0800, Dan Harkless wrote: > >I would suggest having the Cygwin webmaster update > > to make the PCYMTNQREAIYR policy very clear > >(right now there's only a vague

Re: 1.5.21-1: sshd: "child_copy: linked dll data write copy failed" after computer reboot (Windows 2000 SP4)

On Tue, Nov 07, 2006 at 11:03:30PM -0800, Dan Harkless wrote: >I would suggest having the Cygwin webmaster update > to make the PCYMTNQREAIYR policy very clear >(right now there's only a vague hint at it with "...viewable by anyone. That >includes email addresses..."),

Re: 1.5.21-1: sshd: "child_copy: linked dll data write copy failed" after computer reboot (Windows 2000 SP4)

On November 7, 2006, "Larry Hall (Cygwin)" wrote: > > No. Another application using a different cygwin1.dll would have to be > running. As long as it is, the old cygwin1.dll is loaded in memory and > will cause conflicts. Kill'em. Okay. Good to know. Would the other copy need to be called c

Re: 1.5.21-1: sshd: "child_copy: linked dll data write copy failed" after computer reboot (Windows 2000 SP4)

On November 7, 2006, Igor Peshansky wrote: > On Tue, 7 Nov 2006, Dan Harkless wrote: > > On November 7, 2006, Dan Harkless <[EMAIL PROTECTED]> wrote: > > (yes, even your own -- do you > really want more spam?). Thanks. Argh. Sorry. I guess I am used

Re: 1.5.21-1: sshd: "child_copy: linked dll data write copy failed" after computer reboot (Windows 2000 SP4)

Dan Harkless wrote: However, I have had issues in the past few months where suddenly commands in my bash window would start failing with the "probably due to using incompatible versions of the cygwin DLL" error (without crash popups). When that first occurred, I did a search and found no othe

Re: 1.5.21-1: sshd: "child_copy: linked dll data write copy failed" after computer reboot (Windows 2000 SP4)

host-config told it not to use privilege separation, to see if that would make any difference, but after rebooting, sshd is doing the: 13 [main] sshd 1208 child_copy: linked dll data write copy failed, 0x33F000..0x33F050, done 0, windows pid 2276708, Win32 error 487 bit again. '

Re: 1.5.21-1: sshd: "child_copy: linked dll data write copy failed" after computer reboot (Windows 2000 SP4)

safety copy of the cygwin1.dll file, told setup.exe it could delete it, it failed to do so, and then I deleted it with Windows Explorer and then deleted C:\cygwin and restarted the install once more from scratch. After rebooting, as I mentioned, sshd's "child_copy: linked dll data write copy fa

Re: 1.5.21-1: sshd: "child_copy: linked dll data write copy failed" after computer reboot (Windows 2000 SP4)

when running > ssh-host-config told it not to use privilege separation, to see if that > would make any difference, but after rebooting, sshd is doing the: > >13 [main] sshd 1208 child_copy: linked dll data write copy failed, > 0x33F000..0x33F050, done 0, windows pid 22767

Re: 1.5.21-1: sshd: "child_copy: linked dll data write copy failed" after computer reboot (Windows 2000 SP4)

Dan Harkless wrote: Double argh. After rebooting, I found sshd wasn't running at all. Looking at /var/log/sshd.log, I found a ton of: C:\cygwin\usr\sbin\sshd.exe (1584): *** proc magic mismatch detected - 0x704D1F7E/0xD079E02. This problem is probably due to using incompatible versions of t

Re: 1.5.21-1: sshd: "child_copy: linked dll data write copy failed" after computer reboot (Windows 2000 SP4)

on, retry 0, exit code 0x80, errno 11 > > errors. The second two copies had "91234694" and "96508326" instead of "16" > but were otherwise identical. (It would certainly be helpful if these > errors had timestamps, BTW.) > > Trying 'net start s

Re: 1.5.21-1: sshd: "child_copy: linked dll data write copy failed" after computer reboot (Windows 2000 SP4)

On November 7, 2006, Dan Harkless <[EMAIL PROTECTED]> wrote: > On November 7, 2006, Brian Dessent <[EMAIL PROTECTED]> wrote: > > Dan Harkless wrote: > > > > > Does this mean setup.exe should be modified to do a rebaseall as the final > > > step of installation, so fresh installs of Cygwin won't b

1.5.21-1: sshd: "child_copy: linked dll data write copy failed" after computer reboot (Windows 2000 SP4)

Changed the Subject from '1.5.19-4: sshd: "child_copy: linked dll data write copy failed" after computer reboot (Windows 2003 Server SP1)'. On November 7, 2006, Brian Dessent <[EMAIL PROTECTED]> wrote: > Dan Harkless wrote: > > > Does this mean setup.ex

Re: 1.5.19-4: sshd: "child_copy: linked dll data write copy failed" after computer reboot (Windows 2003 Server SP1)

Dan Harkless wrote: > Does this mean setup.exe should be modified to do a rebaseall as the final > step of installation, so fresh installs of Cygwin won't be broken > out-of-the-box? This has been discussed in the past. It's not a good idea, because: - rebaseall is not always needed, only in ce

Re: 1.5.19-4: sshd: "child_copy: linked dll data write copy failed" after computer reboot (Windows 2003 Server SP1)

member the details, multiple things had been proposed and tried, but there was ultimately no solution. I didn't want to go back over the same ground. > > [...] > > 13 [main] sshd 1144 child_copy: linked dll data write copy failed, > > 0x33F000..0x33F050, don

Re: 1.5.19-4: sshd: "child_copy: linked dll data write copy failed" after computer reboot (Windows 2003 Server SP1)

On Nov 6 20:51, Dan Harkless wrote: > > [Sigh. was it really necessary to full-quote such a long mail?] > [...] > 13 [main] sshd 1144 child_copy: linked dll data write copy failed, > 0x33F000..0x33F050, done 0, windows pid 2276708, Win32 error 487 > [...] > Hel

Re: 1.5.19-4: sshd: "child_copy: linked dll data write copy failed" after computer reboot (Windows 2003 Server SP1)

t on 3(!) machines with the same configuration and the problem can > be reliably reproduced on each one of them. > I found some similar threads in earlier discussions, but without a solution > for me, for instance: > http://www.cygwin.com/ml/cygwin/2006-04/msg00660.html >

Re: 1.5.19-4: sshd: "child_copy: linked dll data write copy failed" after computer reboot (Windows 2003 Server SP1)

I wouldn't believen the result, too ;-) > > and in in /var/log/sshd.log appears again the good old song: > > -------------------- > > 9 [main] sshd 2556 child_copy: linked dll

Re: 1.5.19-4: sshd: "child_copy: linked dll data write copy failed" after computer reboot (Windows 2003 Server SP1)

Hi Larry, that's what I already did, used the "-i" flag. Please just give it a try - registering a service using cygrunsrv with another account (user name, password) using "-i" - it won't work. Believe me that I tried what I wrote here ;-) R.K. On Friday 02 June 2006 17:42, Larry Hall (Cygwin)

Re: 1.5.19-4: sshd: "child_copy: linked dll data write copy failed" after computer reboot (Windows 2003 Server SP1)

n in /var/log/sshd.log appears again the good old song: > ---- > 9 [main] sshd 2556 child_copy: linked dll data write copy failed, > 0x46C000..0x46C040, done

Re: 1.5.19-4: sshd: "child_copy: linked dll data write copy failed" after computer reboot (Windows 2003 Server SP1)

On Fri, Jun 02, 2006 at 11:42:27AM -0400, Larry Hall (Cygwin) wrote: >On 06/02/2006, Ren? Krell wrote: >>The main reason for using the LocalSystem account instead of a >>different one is that I want to allow interactive applications to >>appear in Windows, which isn't definitely allowed by cygrunsr

Re: 1.5.19-4: sshd: "child_copy: linked dll data write copy failed" after computer reboot (Windows 2003 Server SP1)

On 06/02/2006, René Krell wrote: The main reason for using the LocalSystem account instead of a different one is that I want to allow interactive applications to appear in Windows, which isn't definitely allowed by cygrunsrv and probably generally in Windows with a separated sshd account. In

Re: 1.5.19-4: sshd: "child_copy: linked dll data write copy failed" after computer reboot (Windows 2003 Server SP1)

[EMAIL PROTECTED]:~> ssh [EMAIL PROTECTED] ssh_exchange_identification: Connection closed by remote host and in in /var/log/sshd.log appears again the good old song: ---- 9

Re: 1.5.19-4: sshd: "child_copy: linked dll data write copy failed" after computer reboot (Windows 2003 Server SP1)

Hi René, The note about Windows 2003 Server and ssh-host-config I noticed but ignored, because the reasons for doing this mentioned there were obviously different from my problem. Either you have a permission to do something or not, but not only sometimes (after simply restarting the service).

Re: 1.5.19-4: sshd: "child_copy: linked dll data write copy failed" after computer reboot (Windows 2003 Server SP1)

René Krell wrote: > I installed Cygwin rel. 1.5.19-4 on Windows 2003 Server SP1. [snip] > After installing I launched ssh-host-config and activated the sshd system > service. [snip] > Service : sshd > Display name: CYGWIN sshd > Current State : Running > Controls Accepte

1.5.19-4: sshd: "child_copy: linked dll data write copy failed" after computer reboot (Windows 2003 Server SP1)

moment in /var/log/sshd.log occurs an entry like this: --- 8 [main] sshd 2060 child_copy: linked dll data write copy failed, 0x46C000..0x46C040, done 0, windows pid 2284756, Win32 error 87 --- If I restart the sshd system service only without restarting the computer the connectivity works as

Re: child_copy: linked dll data write copy failed

ld_copy: linked dll data write copy failed I had cygwin running just fine on my laptop, but my simple startxwin.cmd (run from cmd.exe) script started failing. In stepping through it, I found that I was getting "child_copy: linked dll data write copy failed" error on xrdb, which appear

child_copy: linked dll data write copy failed

I had cygwin running just fine on my laptop, but my simple startxwin.cmd (run from cmd.exe) script started failing. In stepping through it, I found that I was getting "child_copy: linked dll data write copy failed" error on xrdb, which appears to be when it runs cpp. I upgraded to cygwi