pseudo-hang during postinstall

View: New views
2 Messages — Rating Filter:   Alert me  

pseudo-hang during postinstall

by Jeffrey Friedl :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message


Hi,
Using the latest 1.7 on XP SP3, installs seem to hang during the pre/post
install phases, as if it's being blocked by a BLODA. However, it persists
even after fully uninstalling any and every security-related item I could
find (I didn't have much), stopping and disabling almost every service, and
eradicating any mention of "logitec" and "norton" from the registry.

Unlike mentions of BLODA I've seen, the processes eventually do seem to
continue if I leave them long enough. A bunch of zombie bash.exe process
accumulate, but the install does seem to be successful. Eventually.

Here's perhaps an interesting tidbit: if I try to shut down without killing
every bash.exe the install process has left behind, the machine is 100%
unresponsive for 15-20 seconds until the "bash.exe is not responding"
message pops up and I kill it, then again for 15-20 seconds for the next,
and so on.

Once it's working, it's working, except that I can't start sshd as a
service. If I open a shell and run /usr/sbin/sshd by hand, it's fine.

Does any of this ring a bell?

Thanks,
        Jeffrey
--------------------------------------------------------------------------
Jeffrey Friedl           Kyoto, Japan              http://regex.info/blog/

--
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: pseudo-hang during postinstall

by Larry Hall (Cygwin) :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

On 10/28/2009 09:36 PM, Jeffrey Friedl wrote:
> Once it's working, it's working, except that I can't start sshd as a
> service. If I open a shell and run /usr/sbin/sshd by hand, it's fine.
>
> Does any of this ring a bell?

Other than the part about sshd, no.  As for sshd, since you've run it
by hand, and I'm assume you didn't do so from a LocalSystem-owned
shell, you're guaranteed that you won't be able to run it as a service
now without undoing everything that you did (and most of that is stuff
that I'm sure you didn't realize you were doing at the time).  If you
never plan to allow more than the user you're running the service as
to log in with sshd, then that's OK.  Otherwise, you have a problem.
Sorry if this sounds harsh. I'm just not a fan of reading the plight of
people on this list that can't get sshd running because of this.  I know,
in your case you couldn't get it to run as a service before this.  But
now, you're further away from being able to do it, if that's ever a goal.

--
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