Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
Message-ID:	<3D820A2B.D111A128@morganstanley.com>
Date:	Fri, 13 Sep 2002 16:54:19 +0100
From:	Robert White <Robert DOT White AT morganstanley DOT com>
Reply-To:	Robert DOT White AT morganstanley DOT com
Organization:	Morgan Stanley
X-Accept-Language:	en,pdf
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	inetd stops allowing connections after console login

Hi

Hopefully I haven't missed this in the archives, I have looked in google
quite extensively.

I have observed the following behaviour with inetd.

Boot box, inetd starts as a service, everything works perfectly. Connect
multiple times from remote boxes using telnet / rexec etc.

Log in to actual box where inetd is running, still no problems.

Log off from box where inetd is running, log back on as a different
account.

Inetd still running, exsiting remote connections still ok, but inetd is
unable to spawn new connections. I have tested this quite extensively
and it is not a resource limit as I first thought, nor is it a max
number of connections problem.

Has anyone seen behaviour like this before?

BTW this is NT 4 workstation sp 6a.

Thanks in advance.

Regds

Rob White


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -