Message-ID: <11950121.post@talk.nabble.com>
Date: Wed, 1 Aug 2007 10:21:48 -0700 (PDT)
From: patrickinminneapolis <patrickinminneapolis AT gmail DOT com>
To: cygwin AT cygwin DOT com
Subject: The Solution to Ctrl-C problems
In-Reply-To: <11574352.post@talk.nabble.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
References: <11574352 DOT post AT talk DOT nabble DOT com>
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com


This isn't exactly a cygwin fix, but this is what worked for my problem.  

I needed a consoleapp launcher to start up when the machine starts. 
Then I use ssh to give consolelauncher arguments of what console app to
launch
Then I use ssh to launch another program I wrote in C# which uses
AttachConsole and GenerateCtrlCEvent to send a CtrlC to the desired console.
From there I control the console with stdin and stdout redirection as one
would expect. 

Kind of a pain in the 

but whatever. 
-- 
View this message in context: http://www.nabble.com/kill--2-is-too-powerful-tf4072624.html#a11950121
Sent from the Cygwin Users mailing list archive at Nabble.com.


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