Mailing-List: contact cygwin-apps-help AT sourceware DOT cygnus DOT com; run by ezmlm Sender: cygwin-apps-owner AT sourceware DOT cygnus DOT com List-Subscribe: List-Archive: List-Post: List-Help: , Delivered-To: mailing list cygwin-apps AT sources DOT redhat DOT com X-Envelope-Sender-Is: Andrej DOT Borsenkow AT mow DOT siemens DOT ru (at relayer david.siemens.de) From: Borsenkow Andrej To: cygwin-apps AT cygwin DOT com Subject: RE: Proposed RPM Installer Design Date: Mon, 30 Jul 2001 16:21:31 +0400 Message-ID: <006601c118f2$2aa715f0$21c9ca95@mow.siemens.ru> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) In-Reply-To: <15203.4909.782758.517882@coyote.priv.helixdigital.com> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2479.0006 Quoting the design document: ============ - The user can manually shutdown the running Cygwin applications, and after doing so, can retry the installation. - The user can have the launcher automatically shutdown the running Cygwin applications, which will result in cygwin1.dll being unloaded from memory. [***NOTE*** The best way to shutdown the apps would be to send them a SIGHUP first, waiting for a few seconds, and then sending them a SIGTERM, mimicking the way Unix shuts down. However, this would require dynamically loading the Cygwin DLL and calling signal(). I don't know if this is actually possible.] - The user can terminate the installation. ============= What about services? You have at least two problems here: - normal user usually cannot stop service. This is part of more general problem - assuming that the original installation was done as administrator (a must for system-wide installation) can installer detect if normal user tries to run it? It may result in partial and thus broken installation. OTOH it is pretty possible for several users to have private Cygwin installations. - is it enough to just kill service process? Won't it be interpreted by Windows as service failed (probably yes)? On Unix it is done as part of RPM pre/post script (service stop inetd/service start inetd), but we are trapped on Windows as the above should happen before RPM runs. I do not see easy solution here. -andrej