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
X-Server-Uuid: 2d3b7162-db1d-11d3-b8ee-0008c7dfb6f1
Message-ID: <718198F862F1D411B10F0002A50A4DB1059FE8E2@e90wwce3.dx.deere.com>
From: "Polley Christopher W" <PolleyChristopherW AT JohnDeere DOT com>
Reply-to: cygwin AT cygwin DOT com
To: "'cygwin AT cygwin DOT com'" <cygwin AT cygwin DOT com>
Subject: RE: bash failed to initialize on telnet/rsh/rlogin server
Date: Wed, 27 Mar 2002 09:05:20 -0600
MIME-Version: 1.0
X-WSS-ID: 10BF003213564-01-02
Content-Type: text/plain; 
 charset=us-ascii
Content-Transfer-Encoding: 7bit

Thanks, David,

	>This happened to me on NT4 when I upgraded to cygwin-1.3.10, and
was
	>*not* using ntsec.  Using ntsec fixed it.  Is ntsec set early
enough
	>for inetd?  (And are you rebooting when making changes?)  Does the
	>inetd service have sufficient user rights?  Is everything

	I had ntsec set... but had not rebooted since setting it.  Rebooted,
and 
	now all is well :-) (closing all cygwin processes including 'net
stop 
	inetd' wasn't enough)


	So now that I know how to isolate the problem, is there a way to
strace a daemon?


	Warm regards,

	Chris



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