Message-Id: <200604061951.k36JpYtr032461@tigris.pounder.sol.net>
From: cygwin AT trodman DOT com (Tom Rodman)
Reply-to: cygwin AT cygwin DOT com
To: cygwin AT cygwin DOT com
Subject: Re: when is using cygserver recommended? (thx)
In-reply-to: <20060406174658.GE8592@trixie.casa.cgf.cx>
References: <200604061637 DOT k36GbUjs031543 AT tigris DOT pounder DOT sol DOT net> <20060406174658 DOT GE8592 AT trixie DOT casa DOT cgf DOT cx>
Date: Thu, 06 Apr 2006 14:51:34 -0500
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

On Thu 4/6/06 13:46 EDT cgf wrote:
--snip
> >I just read 
> >
> >  /usr/share/doc/cygwin-doc-1.4/html/cygwin-ug-net/using-cygserver.html
> >
> >for the first time.  
> >
> >We mainly run fairly straight forward bash and perl scripts under
> >cygwin, both at the commandline and through cron; some scripts use
> >make, some use background processes and "wait". 
> >
> >At what point does it make sense to start using the cygserver service?
> >Some guidelines for nondeveloper types in this topic would be
> >appreciated- I did check the FAQ.
> 
> If you don't know if you need it, you don't need it.
> 
> cgf

fair enough, thanks.  

My interest was only in reducing the chances of "fork problem" 
( http://cygwin.com/ml/cygwin/2006-04/msg00122.html ).

--
Tom

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