Mailing-List: contact cygwin-developers-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT cygwin DOT com Delivered-To: mailing list cygwin-developers AT cygwin DOT com From: "Robert Collins" To: "'Conrad Scott'" , "'Charles Wilson'" Cc: Subject: RE: System-wide mutexes and pthreads Date: Fri, 14 Jun 2002 00:23:23 +1000 Message-ID: <009d01c212e5$e0804a70$0200a8c0@lifelesswks> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal Importance: Normal In-Reply-To: <02f801c21263$939939b0$6132bc3e@BABEL> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 > -----Original Message----- > From: cygwin-developers-owner AT cygwin DOT com > [mailto:cygwin-developers-owner AT cygwin DOT com] On Behalf Of Conrad Scott > Sent: Thursday, 13 June 2002 8:51 AM > My only thought on this was that not depending on the cygwin > dll might give > us the flexibility if we wanted cygserver to be started > before any cygwin > processes (and it can't start before itself . . .). Then again I can't > imagine what sort of requirement there might be for that. I can't either. Lets cross that bridge IFF we need to. We can always copy out any cygwin core code that's needed. > More pertinently we should think about making sure that at > least some things > work if the daemon is killed and re-started while there are > cygwin programs > running. But I don't think that's an immediate concern. This is orthogonal: whether cygserver uses cygwin1.dll or not, killing cygserver will affect all other cygwin process in the same fashion. Rob