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
To: cygwin AT cygwin DOT com
From: Rolf Campbell <thats DOT unpossible AT gmail DOT com>
Subject: rsync throttling (Was: children of init ignore STOP and CONT signals)
Date: Tue, 22 Feb 2005 17:12:09 -0500
Lines: 15
Message-ID: <421BAE39.9040104@gmail.com>
References: <BAY1-F321629E2FEB020E1F60A3BDB620 AT phx DOT gbl>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Complaints-To: usenet AT sea DOT gmane DOT org
X-Gmane-NNTP-Posting-Host: ottgw.tropicnetworks.com
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
In-Reply-To: <BAY1-F321629E2FEB020E1F60A3BDB620@phx.gbl>
X-Gmane-MailScanner: Found to be clean
X-Gmane-MailScanner: Found to be clean
X-MailScanner-From: goc-cygwin AT m DOT gmane DOT org
X-MailScanner-To: cygwin AT cygwin DOT com
X-IsSubscribed: yes

Sam Inala wrote:
> Cygwin 1.5.12(0.116/4/2) on W2K SP4
> 
> Not all signals are ignored. The TERM and INT signals correctly 
> terminate the process. I would like to send STOP and CONT to throttle 
> the CPU usage of a rsync process. I want to avoid spawning a bash 
> process to start rsync because it is started from a Windows process. If 
> I invoke a shell process to invoke rsync, it will be difficult to get 
> the windows process id so I can translate it to a cygwin process id and 
> send it a signal.
> 
> Any suggestions?
Use --bwlimit=KBPS.  This should indirectly throttle cpu usage.  This 
won't have an impact on the initial cpu-usage if you specify -c to force 
check-summing of all files.


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