Re: SSH - Can't Login (3rd Post)

[J.C. Wren]

On Thu, Oct 28, 2010 at 11:02 PM, Larry Hall (Cygwin)
 wrote:
> On 10/28/2010 10:37 PM, Brian Wilson wrote:
>>
>> The ssh command and its response are just a cut and paste of the bash
>> screen.
>> Trying to execute ssh -v ncc-1701 gives exactly the same results (note
>> there
>> is no -v option in the displayed list).
>
> $ ssh wil...@ncc-1701
> usage: ssh [-1246AaCfgKkMNnqsTtVvXxYy] [-b bind_address] [-c cipher_spec]...
>                                ^
> There it is. ;-)
>
> I really didn't doubt that you cut and paste the output once I looked at
> it but I'm glad you confirmed it.
>
>> I've attached a new cygcheck output (-svr) as you suggested.  One thing I
>> noted was that the uname -a output says I have Cygwin 1.7.1 and this
>> confuses me.  I've updated on a regular basis and reboot whenever the
>> installation requests me to do so.  I should have the 1.7.7-1 release.
>>  The
>> cygcheck seems to have differing 1.7* information.  Is there some magic
>> translation I need to know of to get the correct release number?
>
> No, if it's reporting 1.7.1, I expect that's the version you're running.
> And I expect that's coming into play here.  But go ahead and double check
> it in the Windows explorer.  I expect you'll find it reports 1.7.1 too.
>
> This is a problem.  I expect you know that you need to stop all your
> services before an upgrade in order to get the new DLL moved into place
> immediately, right?  If you don't do this, it will queue up the move for
> next reboot.  My guess is you've rebooted at least once since installing
> 1.7.x > 1.7.1 but it's possible things have gotten gummed up if you didn't
> and have since done other upgrades (that's pure theory though).  What's
> not is that you have ZoneAlarm installed that is known to cause problems.
> I'd recommend unstalling it, stopping all Cygwin services (cron, cygserver,
> httpd2, and sshd), reinstall the Cygwin package, and then restart the
> services.  You should find this process gives you a current cygwin1.dll
> in '/bin'.  If not, we need to look at the results of the installation
> process (and/or for  ).
>
> --
> Larry Hall                              http://www.rfk.com
> RFK Partners, Inc.                      (508) 893-9779 - RFK Office
> 216 Dalton Rd.                          (508) 893-9889 - FAX
> Holliston, MA 01746
>
> _
>
> A: Yes.
>>
>> Q: Are you sure?
>>>
>>> A: Because it reverses the logical flow of conversation.

 Q: Why is top posting annoying in email?
>
> --
> Problem reports:       http://cygwin.com/problems.html
> FAQ:                   http://cygwin.com/faq/
> Documentation:         http://cygwin.com/docs.html
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
>

I'm pretty convinced there's something going on (or NOT going on...)
during the upgrade process.  I've seen this report of someone doing a
setup and still having an old cygwin1.dll, it's happened to me (see
thread regarding svn metadata name mangling), and I've had someone
email me about the name mangling issue (who didn't want to post to the
list) discover he had a downlevel version of the cygwin1.dll file
also.

There's also the additional evidence of finding a half dozen or so
files ending in .new /usr/bin and /usr/sbin.  Perhaps Microsoft had a
hotfix or somesuch that might have affected Cygwin when it needs to do
a replace files on boot thing.  I have no idea how that's implemented,
so that's speculation, of course.

--jc

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple

Re: SSH - Can't Login (3rd Post)

[J.C. Wren]

On Wed, Oct 27, 2010 at 4:02 AM, Charles Smith  wrote:
> The critical information is that ssh works fine by using setup.exe to 
> back-configure version 5.5p?.? (the previous version) with no other changes.  
> Completely reliably, for different users on different machines.
>
>
>
>
> --
> Problem reports:       http://cygwin.com/problems.html
> FAQ:                   http://cygwin.com/faq/
> Documentation:         http://cygwin.com/docs.html
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
>

I ran into this also, the other day.  Check the cygwin1.dll version
(with cygcheck).

--jc

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple

Re: Subversion mangling names in .svn/entries metadata file

[J.C. Wren]

Do you *really* think I didn't reboot it?  C'mon now, be serious.
I've been using Cygwin for at least 5 years, I think I can follow some
instructions when setup tells me I'll need to.

I think I ended up rebooting 12 times, or at least that what it seemed like.

Maybe I didn't explicitly say that I did reboot the system, but that's
not a reason to merely assume that I didn't.

In any case, it made no difference.  There were half a dozen files
ending in .new in /usr/bin and /usr/sbin, so *something* wasn't
running that was supposed to move them after a reboot.

--jc

Eagles may soar, but weasels don't get sucked into jet engines.


On Tue, Oct 26, 2010 at 8:12 AM, Jeremy Bopp  wrote:
>
> On 10/26/2010 05:58 AM, J.C. Wren wrote:
> > OK, I did several things.  First, I downgraded subversion to 1.6.12
> > and everything worked.  Then I re-ran the installer and re-installed
> > the base cygwin package, which should have upgraded the DLL.  It did
> > not, It was still at 1.7.5.  I'm using setup 2.721,
> > http://mirrors.kernel.org for the site, the installer says the package
> > installed is 1.7.7-1.  I then manually deleted the cygwin1.dll and ran
> > setup.exe again.  THIS time it upgraded the DLL.  The DLL's don't have
> > any weird permission, so I don't know why it didn't upgrade.  I did
> > have sshd running, and setup threw a warning that I'd need to reboot.
> > Maybe something related to that?
> >
> > Anyway, at this point, I now appear to be able to use subversion
> > without filename mangling.  I'm just curious why multiple installs of
> > the cygwin base didn't update the cygwin1.dll.
> >
> > Very weird!
>
> Setup.exe warned you that a file was in use and then told you to reboot
> in order to complete your installation, and yet you think it's weird
> that your installation is incomplete without a reboot.  Hmmm
>
> Anyway, this is a well known problem with Windows.  Files that are in
> use, such as cygwin1.dll when sshd is running, cannot be immediately
> replaced.  If you want to replace them, you must either ensure they are
> not in use (by stopping sshd and any other Cygwin process in this case)
> or schedule them to be replaced upon reboot (which is precisely what
> setup.exe does for you) and then actually reboot. :-)
>
> -Jeremy
>
> --
> Problem reports:       http://cygwin.com/problems.html
> FAQ:                   http://cygwin.com/faq/
> Documentation:         http://cygwin.com/docs.html
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple

Re: Subversion mangling names in .svn/entries metadata file

[J.C. Wren]

On Sat, Oct 23, 2010 at 12:34 AM, Andy Koppe  wrote:
>
> On 22 October 2010 18:51, J.C. Wren wrote:
> > I updated my Cygwin install a couple days ago, and have ran into a
> > problem with Subversion mangling the .svn/entries file.
> >
> > Before the problem occurred, I had done a 'svn status' with no issues.
> >  I committed a file, ran 'svn status' again, and received the
> > following error message:
> >
> >   svn: Error at entry 1 in entries file for '.':
> >   svn: Invalid escape sequence
> >
> > Looking in the .svn/entries file, the first file name should read
> >
> >     http://amzatlanta.com/svn_amzatlanta/sx_gfm/trunk
> >     http://amzatlanta.com/svn_amzatlanta/sx_gfm
> >
> > but is actually encoded as
> >
> >     
> > h\x74\x74p://\x61mz\x61\x74l\x61n\x74\x61.\x63\x6f\x6d/\x73\x76n_\x61mz\x61\x74l\x61n\x74\x61/\x73\x78_g\x66\x6d/\x74\x72\x75nk
> >     
> > h\x74\x74p://\x61mz\x61\x74l\x61n\x74\x61.\x63\x6f\x6d/\x73\x76n_\x61mz\x61\x74l\x61n\x74\x61/\x73\x78_g\x66\x6d
> >
> > Attempting to check out the repository into a new directory gives the
> > same error.  On another machine with a slightly older install of
> > Cygwin had no issues.  I was also able to check it out on a Linux box
> > (I did this to make sure the repository hadn't gotten corrupted
> > somehow).
> >
> > One person in #cygwin speculated it might be a locale issue.
>
> Seems unlikely, as the filenames are entirely within the ASCII range.
> I've got no idea though why selected lowercase characters should have
> been replaced with their hex escape equivalents.
>
> The cygcheck output doesn't look healthy though:
>
>    Cygwin DLL version info:
>        DLL version: 1.7.5
>
> cygwin                         1.7.7-1
>
> Also, any chance that TortoiseSVN\bin in the path might interfere? Try
> 'which svn' and 'svn --version' to make sure you're really getting the
> Cygwin version.
>
> $ svn --version
> svn, version 1.6.13 (r1002816)
>   compiled Oct  4 2010, 09:08:12
>
> Andy
>
> --
> Problem reports:       http://cygwin.com/problems.html
> FAQ:                   http://cygwin.com/faq/
> Documentation:         http://cygwin.com/docs.html
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

OK, I did several things.  First, I downgraded subversion to 1.6.12
and everything worked.  Then I re-ran the installer and re-installed
the base cygwin package, which should have upgraded the DLL.  It did
not, It was still at 1.7.5.  I'm using setup 2.721,
http://mirrors.kernel.org for the site, the installer says the package
installed is 1.7.7-1.  I then manually deleted the cygwin1.dll and ran
setup.exe again.  THIS time it upgraded the DLL.  The DLL's don't have
any weird permission, so I don't know why it didn't upgrade.  I did
have sshd running, and setup threw a warning that I'd need to reboot.
Maybe something related to that?

Anyway, at this point, I now appear to be able to use subversion
without filename mangling.  I'm just curious why multiple installs of
the cygwin base didn't update the cygwin1.dll.

Very weird!

--jc

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple