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 X-Authentication-Warning: eos.vss.fsi.com: ford owned process doing -bs Date: Tue, 25 Nov 2003 13:51:32 -0600 (CST) From: Brian Ford X-X-Sender: ford AT eos To: cygwin AT cygwin DOT com Subject: Re: inetd desktop interaction w/o console? In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Sat, 22 Nov 2003, Igor Pechtchanski wrote: > On Sat, 22 Nov 2003, Igor Pechtchanski wrote: > > On Sat, 22 Nov 2003, Brian Ford wrote: > > > I know this has been discussed lots before, but I just spent the last few > > > hours googling, archive searching, trying run.exe, etc. without finding a > > > solid answer. > > > > > > What are the known issues around allowing Cygwin's inetd to interact with > > > the desktop, but without showing the console window? > > > > > > It would be a real nice feature for us to just add that service option > > > and have it work without the distracting console window. So, I thought > > > I'd ping about the known issues before wasting more hours trying to get it > > > working. > > > > > > In the end, I am expecting to contribute a patch to inetd allowing this if > > > it is reasonably possible. So, I'm not looking for a handout, just a > > > jumping off point. > > > > > > Thanks. > > > > /usr/X11R6/bin/run.exe > > Also . > Like I stated above, I had tried run.exe. But, I think its auto backgrounding fooled both me and the service manager into thinking it didn't work. Maybe adding a -no-background, or some such option, to run.exe would fix this. So, the only way to do this is via special arguments to CreateProcess, or to compile with -mwindows? > Oops, forgot to add that this would probably be more useful as a patch to > cygrunsrv (unless you mean running "inetd --install-as-service"). > Well, yes and yes. At the time, I did not have inetd source, so I was unsure exactly how to emulate inetd --install-as-service via cygrunsrv. Incidentally, why does inetd not use cygrunsrv? Just history, I guess. Anyway, I know there has been lots of work around getting windows console output from net, etc. to show up in an rlogin, telnet, ssh, etc. window. Would hiding the console mess this up? Also, when if ever is the console window desireable for inetd, cygrunsrv spawned stuff, etc.? Maybe hiding should be the default if I figure out how. I've got a lot of digging to do to understand any of this, obviously. Thanks for the hand hold. -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444 -- 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/