Message-Id: <200604061637.k36GbUjs031543@tigris.pounder.sol.net>
To: cygwin AT cygwin DOT com
From: cygwin AT trodman DOT com (Tom Rodman)
Reply-to: cygwin AT cygwin DOT com
Subject: when is using cygserver recommended? (I read the FAQ)
Date: Thu, 06 Apr 2006 11:37:29 -0500
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com

On Thu 4/6/06 10:10 EDT "Luis P Caamano" wrote:
> On 6 Apr 2006 03:44:22 -0000, cygwin-digest-help AT cygwin DOT com
> <cygwin-digest-help AT cygwin DOT com> wrote:
> >
> 
> > fork problem
> >         120469 by: david AT adboyd DOT com (J. David Boyd)
> 
> I started using cygserver and edited its config file to use 310 procs
> instead of 62.  In /etc/cygserver.conf, I edited the following:
--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.

--
I see the fork errors once every couple of weeks or so. As Igor
suggested, once the problem is there, it often persists, until you
kill (or exit) all cygwin processes. So far I don't recall a case
where killing all cygwin processes did not fix the problem. I've tried
adjusting the 48MB windows SharedSection heap settings, and I still get
the fork errors.

--
thanks much,
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/