Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com Message-ID: <050601c0e9d3$9d0dea40$0200a8c0@lifelesswks> From: "Robert Collins" To: "cygdev" References: <20010531124452 DOT G1870 AT cygbert DOT vinschen DOT de> <48146951254 DOT 20010531164356 AT logos-m DOT ru> <20010531151226 DOT I1870 AT cygbert DOT vinschen DOT de> Subject: Re: [RFD]: Egor's proposal for a Cygwin server process Date: Thu, 31 May 2001 23:14:23 +1000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-OriginalArrivalTime: 31 May 2001 13:05:50.0748 (UTC) FILETIME=[6A9D6DC0:01C0E9D2] ----- Original Message ----- From: "Corinna Vinschen" > As I wrote in my previous mail, it's essential to be sure about > the process which calls the server. Faking of pid, uid and gid > must not be possible! > Doesn't that imply that the server must spawn every process? Or at least be the caller of the win32 to start the process and setup the process<->server communication channel? Rob