Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Wed, 6 Oct 2004 12:17:49 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: [PATCH] cygrunsrv --recovery Message-ID: <20041006101749.GW6702@cygbert.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <42404 DOT 193 DOT 16 DOT 155 DOT 145 DOT 1096475468 DOT squirrel AT webmail DOT kainz DOT com> <20040930153543 DOT GC29206 AT cygbert DOT vinschen DOT de> <20040930161545 DOT GC26915 AT cygbert DOT vinschen DOT de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2i On Oct 6 11:57, Rainer Hochreiter wrote: > well, are there any guidelines how to submit patches and describing > ChangeLog syntax available? http://cygwin.com/contrib.html, section "When you have finalized your changes" Just ignore the hint to send patches to the cygwin-patches list. > right! but if using ChangeServiceConfig2() is prohibited, why not writing > also directly to registry? Erm?!? Of course you should write directly to the registry. That's how writing the description field is implemented to stay NT4 compatible. So just copy the behaviour for writing the actions parameter. > ok, maybe there is no public documentation > available for that. what i found out is, that SCM writes into a key named > 'FailureActions' of type REG_BINARY. anyone out here, who knows what to write > there? best would be the source of the sc.exe command ;-) I guess the easy way is to use ChangeServiceConfig2 with different arguments and look what it creates as result. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader mailto:cygwin AT cygwin DOT com Red Hat, Inc. -- 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/