Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
From: "Matt Ross" <m DOT g DOT ross AT herts DOT ac DOT uk>
To: <cygwin AT cygwin DOT com>
Subject: Re: A vexing installation problem
Date: Tue, 30 Nov 2004 13:50:03 -0000
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Message-Id: <E1CZ8OP-0001VP-00@altair.herts.ac.uk>
X-UH-MailScanner: No Virus detected
Note-from-DJ: This may be spam

I too have been experiencing this whole problem on a hp DL360G3 server that
up until recently was happily running Cygwin and SSH. When I did a Cygwin
update about a fortnight ago I didn't notice anything was wrong until I
rebooted the server. Then SSH would not start. As it turns out, nearly all
the Cygwin binaries will not start, including sh, bash, mkpasswd, mkgroup.
The strace command works though and I was able to 'strace sh.exe', it always
exits at this point:

66017 13081760 [main] sh 3808 sigproc_init: process/signal handling
enabled(1)

A reinstall from scratch [after rebooting] makes no difference, and the
post-install scripts all fail because sh is not running correctly. While it
has successfully started once since this problem occurred, after the next
reboot it failed again and I haven't been able to get it running ever since.

What was the last version of Cygwin before signal handling was enabled? I
will have to go back to that version if it's possible.

Thanks,

Matt Ross



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