Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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
From: "Dave Korn" <dave DOT korn AT artimi DOT com>
To: <cygwin AT cygwin DOT com>
Subject: RE: Alternative to Cron Jobs with cygrunserv
Date: Tue, 30 Aug 2005 18:32:27 +0100
MIME-Version: 1.0
Content-Type: text/plain; 	charset="us-ascii"
Content-Transfer-Encoding: 7bit
In-Reply-To: <431338F0.4020904@adelphia.net>
Message-ID: <SERRANONDN4CxpAOAkK000003a0@SERRANO.CAM.ARTIMI.COM>

----Original Message----
>From: M Maki
>Sent: 29 August 2005 17:34


> I then created a Windows batch file that pipes the command I
> want to run to the cygwin.bat file that starts cygwin.
> 
> For example:
> 
> @echo on
> echo ./rsyncbkp.sh | C:\cygwin\cygwin.bat
> echo exit | C:\cygwin\cygwin.bat


  The second 'echo' command is completely superfluous.  The first cygwin
invocation exits as soon as the command has completed.  Even if it didn't,
piping 'exit' into the batch file again is only going to start a new
invocation of cygwin, you can't talk to an existing program that way.



    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....


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