Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Date: Tue, 26 Sep 2000 13:01:54 -0400 (EDT)
From: David Condon <dcondon AT apk DOT net>
X-Sender: dcondon AT newstaff
To: cygwin AT sourceware DOT cygnus DOT com
Subject: sshd from binary package vs. compiled from source -- problem with
 fork()
Message-ID: <Pine.GSO.4.10.10009261245280.10948-100000@newstaff>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Using Cygwin 1.1.4 and latest stable versions installed as of about three
weeks ago.

I am trying to build an sshd with TCP wrappers support and noticing a
slight but significant difference in its behavior from the distributed
binary. I am wondering if any arguments to configure were used for the
binary that I could try.

I installed the binary distribution of OpenSSL and built and installed the
port of TCP wrappers, both without any problems. I installed the binary
distribution of OpenSSH and start sshd using SRVANY, and it works perfectly.

I got the source distribution of OpenSSH and did

./configure --with-tcp-wrappers
make
make install

All the programs work fine, and sshd can still be started from SRVANY. However,
when I go to login I get this in the event log:

The description for Event ID (0) in Source (sshd) could not be found. It
contains the following insertion string(s): sshd: Win32 Process ID = 0x1FA:
Cygwin Process ID = 0x7A0D: error: fork: No more processes.

The same thing happens if I leave out TCP wrappers and simply do ./configure
with _no_ arguments.

If I start sshd manually from the command line, it is able to fork and accept
logins. If built with TCP wrappers support, that part works as well.

So the only known difference is that if I built it, even with no customization,
and start it as a service from SRVANY, it cannot fork, whereas the
distributed binary can.

-- 
David Condon                    |       dcondon AT apk DOT net
Webmaster, APK Net Ltd.         |       (216) 241-7166
1621 Euclid Ave., Suite 1230    |       Fax: (216) 241-7522
Cleveland, Ohio 44115


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com