X-Spam-Check-By: sourceware.org Date: Sat, 8 Apr 2006 14:37:35 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: when is using cygserver recommended? (thx) Message-ID: <20060408183735.GA1477@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.11 Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On Sat, Apr 08, 2006 at 01:25:13PM -0400, Luis P Caamano wrote: >> ---------- Forwarded message ---------- >> From: (J. David Boyd) >> To: cygwin >> Date: Fri, 07 Apr 2006 16:29:59 -0400 >> Subject: Re: when is using cygserver recommended? (thx) >> Christopher Faylor writes: >> >> > >> > In that case, my previous reply is even more pertinent; especially given >> > that Igor mentioned that the problem has nothing to do with cygserver. >> >> Strange then, that my 'fork' problem has now gone away, after adjusting my >> cygserver.conf file.... > >I don't know if it fixes it or not but I can tell you that I started >using cygserver perhaps a couple months ago and after changing that >variable, I've never seen the fork problem again. > >However, I'm not completely sure but I think that the chain of events >was like this: > >1- no fork problems > >2- added cygserver for different reasons > >3- got fork problems > >4- edited cygserver.conf > >5- no fork problems > >Right now, although I understand that fork problem, I do not >understand its cause or why the cygserver.conf change fixed it. I >think the reason I edited that file was because I got the impression >that using cygserver is what caused my fork problems. It seems though >that people are getting the fork problems even when not using >cygserver. I concluded that I needed to research cygserver a lot more >to understand what's going. One day ... > >One thing is certain, though. I'm very glad I don't see the fork >problems anymore. But, think of the chickens... Just to state the obvious again: cygserver has nothing to do with fork -- superstitious assertions to the contrary not withstanding. cgf -- 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/