This is the mail archive of the
cygwin-developers@cygwin.com
mailing list for the Cygwin project.
RE: System-wide mutexes and pthreads
- From: "Robert Collins" <robert dot collins at syncretize dot net>
- To: "'Conrad Scott'" <Conrad dot Scott at dsl dot pipex dot com>,"'Charles Wilson'" <cwilson at ece dot gatech dot edu>
- Cc: <cygwin-developers at cygwin dot com>
- Date: Fri, 14 Jun 2002 00:23:23 +1000
- Subject: RE: System-wide mutexes and pthreads
> -----Original Message-----
> From: cygwin-developers-owner@cygwin.com
> [mailto:cygwin-developers-owner@cygwin.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