Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT sourceware DOT cygnus DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help: <mailto:cygwin-help AT sourceware DOT cygnus DOT com>,
	<http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
Message-ID: <37D00B65.6818EB0C@gc.ehu.es>
Date: Fri, 03 Sep 1999 19:54:45 +0200
From: MoMa <siae0071 AT gc DOT ehu DOT es>
X-Mailer: Mozilla 4.5 [es] (WinNT; I)
X-Accept-Language: es
MIME-Version: 1.0
To: cygwin AT sourceware DOT cygnus DOT com
Subject: Samba 2 running in NT box: almost there !!
References: <8F843C040467 AT panoramix DOT adersa DOT asso DOT fr>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hi,

I have been able to port Samba 2 to an NT box with this setup:
NT 4.0, cygwin Beta 20.1, gcc of this version of cygwin

Well, almost.There is a probleml with the select (cygwin) call in the
samba function sys_select. This select returns inmediately, with
errno=EBADF. This seems akward to me at this point of the server
process, it must be an indicator of a prior error. But the socket opens
correctly some source lines before, and is ready to listen (errno=0).

This prevents the smbd in NT from serving (does not detect the
connection from the client) and the smbclient in NT from receiving the
results of the commands it sends (it connects to a Linux box Samba,
sends commands but does not receive the returning packages).

If we overcome this, Samba will work on NT. I have done a research on
the legal/license implications of this, and look very interesting:
 * The legal limit of 10 connections to an NT workstation dissapear =>
NT server value for NT workstation price, legal.
 * No need for CAL (client access license) to connect to an NT box =>
legal non Win clients, and the NT Terminal server client implications
seem interesting too.

Can someone help withthe select problem?

TIA

Ivan & Ray


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