expected differences
at least from what I could determine roughly).
Eric
- Original Message
From: Corinna Vinschen
To: cygwin@cygwin.com
Sent: Wed, March 17, 2010 7:00:04 AM
Subject: Re: Missing Registry entries under ssh after upgrade from 1.5 to 1.7
On Mar 16 13:03, Eric Berge wrote
>On Apr 2 13:25, Shaddy Baddah wrote:
>> Hi,
>>
>> On 2/04/2010 11:36 AM, Corinna Vinschen wrote:
>> >On Apr 1 14:31, Eric Berge wrote:
>> >>
>> >>I recently updated to 1.7.2 from 1.7.1 with the March 15 development
>> >>pat
y at least 1.7.2 (I think
you'll get 1.7.4 as the default right now).
Also if you want to diagnose this further, trying running
"Process Monitor" from www.sysinternals.com and filter for
the potential failing processes (bash.exe maybe) and look
to see if it's failing on accessing non-existent registry
entries.
Eric Berge
--
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
PD Inc. http://www.pdinc.us -
> - Principal Consultant 10 West 24th Street #100-
> - +1 (443) 269-1555 x333Baltimore, Maryland 21218 -
> - -
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> This message is copyright PD Inc, subject to license 20080407P00.
>
There is a lon
le the example probably
seems a bit bizarre, it's actually something you
> would run into if you
used backticks with ActiveState Perl to execute a
> Cygwin command.
jim
>On Apr 1 14:31, Eric Berge
> wrote:
>
>
> I recently updated to 1.7.2 from 1.7.1 with the
If you're running 1.7.X where X <= 1, this might be fixed by upgrading.
Those versions had a bug where the user's registry was not properly
initialized via ssh. To see if this is your issue, you should be able
to run the "reg query hku" and see if you see your SID listed. Another
symptom of thi
Yeah, it sounds like you're looking at a different problem than
the one I was referring to. That problem did not exist in 1.5.X
as far as I'm aware. Sorry for the false lead.
Eric
- Original Message
> From: JJ Ottusch
> To: cygwin@cygwin.com
> Sent: Sun, April 25, 2010 7:13:14 PM
>
> I'm not sure if this is relevant, but as a domain account user logged directly
> onto 'xxx' I have Administrative privileges, whereas when I use ssh to connect
> to 'xxx' I can access the same resources, but I'm not sure what my privilege
> level is. I know that I am somehow going through the '
> Before 1.7.x came out I had sshd working under cygwin. After upgrading
> it stopped working. I investigated and found the hosts.allow file and
> made the recommended change there. That got my server working to the
> point where I can "ssh localhost" and see the hungry-hungry-hippo. :)
> When I
ge
> From: Steven Collins
> To: cygwin@cygwin.com
> Sent: Thu, May 13, 2010 3:12:40 PM
> Subject: Re: sshd
>
> On Thu, May 13, 2010 at 13:56, Eric Berge <> wrote:
> Anything
> interesting in /var/log/sshd.log or in the event viewer?
>
>
> Eric
>
E
Please let me know if you have any suggestions on how I can
debug the following problem in more detail.
I installed cygwin today on a Windows 2008 (32-bit) server
and bash appears to fail with the following stackdump when
run. I tried various options (such as "bash --version" which
I expected to
ls after initial install on Windows 2008 Server
On May 20 20:02, Eric Blake wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> According to Eric Berge on 5/20/2008 9:52 AM:
> | I installed cygwin today on a Windows 2008 (32-bit) server
>
> I don't have access to Windo
The strace was from a 32-bit Win2008 box. I got the same profile
in an strace from a 64-bit Win2008 box as well, although in that
case the path was the "Unix" form of "/tmp".
As before, any suggestions on how to take this analysis further are
greatly appreciated.
-- Eric
--
Steinar:
Advance warning - I might be reading the problem I'm struggling
with into this...
Take a look at /var/log/setup.log and look at the postinstall
output. I'm suspecting that you're running into a problem I've
seen on 2008 where the bash postinstall fails for some reason
(I've at least se
A nice way to check for being the "right" user is to use
the "whoami" utility - the windows version out in \windows\system32,
not the cygwin one. If it displays that you are "sshd_server" things
are not well.
I still do not fully understand the need to do this, but on some
recent systems I've in
I've seen the same problem for several months now on both 32-bit and 64-bit
versions of 2008. Your /var/log/setup.log probably also shows that most if
not all the postinstall scripts failed for the same reason.
That said, there are other Win2008 boxes I have successfully installed on
and I have
On Jun 25 10:20, Mark J. Reed wrote:
> I know this is a lame suggestion, but I figure it can't hurt to throw
> it out there anyway:
>
> Does explicitly running setup.exe as Administrator make any difference here?
>
> I wouldn't expect it to matter on Vista, but perhaps Server '08, in
> the na
The postinstall scripts might not have run correctly, to really
see what happened with them take a look at /var/log/setup.log
Eric
- Original Message
From: Bryan A. Zimmer <[EMAIL PROTECTED]>
To: cygwin@cygwin.com
Sent: Thursday, July 10, 2008 10:47:32 AM
Subject: Problems installing
18 matches
Mail list logo
