Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Wed, 11 Dec 2002 13:56:09 +0100 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: can user add his own service in cygwin inetd? Message-ID: <20021211135609.P7796@cygbert.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <114780-2200212210223354486@M2W062.mail2web.com> <4.3.1.2.20021210220258.03f0b638@pop.rcn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4.3.1.2.20021210220258.03f0b638@pop.rcn.com> User-Agent: Mutt/1.3.22.1i On Tue, Dec 10, 2002 at 10:32:49PM -0500, Larry Hall (RFK Partners, Inc) wrote: > Sorry, I'm not an inetd expert. I'd be stuck looking at the available > documents too. It's not immediately obvious to me that a perl program > wouldn't be able to be run from inetd but then again, I don't know what > you're doing. If you do exactly what you've done on Linux and it works > there but not with Cygwin, well, then I guess that means there's some > difference that will need to be tracked down. If you're interested in > doing so, you could start with invoking inetd with the -d flag. That > may shed some light. The started application (as e. g. rshd, telnetd, ftpd) have to expect the opened socket descriptors to the client application as stdio file descriptors (0, 1, 2). That should be all you have to check. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:cygwin@cygwin.com Red Hat, Inc. -- 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/