X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org To: cygwin@cygwin.com From: Rob Subject: Re: setup.exe --quiet-mode Date: Wed, 10 Sep 2008 20:24:21 +0000 (UTC) Lines: 19 Message-ID: References: <48C0316C.F9E434A9@dessent.net> <00fc01c90f39$f4006970$9601a8c0@CAM.ARTIMI.COM> <007101c9136b$a62b3e10$9601a8c0@CAM.ARTIMI.COM> <007c01c91372$1c48c3a0$9601a8c0@CAM.ARTIMI.COM> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit User-Agent: Loom/3.14 (http://gmane.org/) X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Dave Korn writes: > That seems like a good start, but it's perhaps just a little bit crude in > the way it handles services; if you kill them stone dead like that, the SCM > will try and restart any that are set for auto-restart-on-fail. It would > probably be a minor improvement if you add an extra bit of bash to shut them > down gracefully by invoking cygrunsrv on them, something a bit like ... > > c:\cygwin\bin\bash.exe --login -c "cygrunsrv -L | xargs -n 1 cygrunsrv -E" > > ... and only then carry on to brute-force kill the leftovers. > > cheers, > DaveK Yeah, I did consider that and try stopping services first. I just left all that out of my post for brevity... at least we're on the same wavelength. Thanks for the input. -- 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/