Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Wed, 20 Aug 2003 13:50:43 +0100 From: Elfyn McBratney To: cygwin AT cygwin DOT com Subject: Re: No output from DOS commands via telnet using xinetd Message-ID: <20030820125042.GC11470@emcb.co.uk> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20030820124206 DOT GB11470 AT emcb DOT co DOT uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030820124206.GB11470@emcb.co.uk> User-Agent: Mutt/1.4.1i Elfyn McBratney wrote: > Brian DOT Kelly AT empireblue DOT com wrote: > > > > "The silence is deafening". Apparently there aren't too many folks using > > telnet with > > xinetd ( I know, I know, SSH is what everyone's doing ). Anyhow, I do have > > a fairly important > > need for this combo, and the problem outlined below is a significant one > > for me. Before I > > do anything else - I would *really* like to know at least, if anyone else > > gets the same behavior. > > That would at least establish that I'm dealing with a legitimate bug rather > > than a setup > > or configuration issue. Just a "me too" - or "works for me" would be MUCH > > appreciated. > > You could try attaching to the xinetd (and inetd) process with strace to see > if there's a noticable difference somewhere. Hmmm... What I meant to say is attach *to* the telnetd processes not the *inetd processes. -- Elfyn -- 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/