Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
From: "Dave Korn" <dk AT artimi DOT com>
To: <cygwin AT cygwin DOT com>
Subject: RE: [PATCH] cygrunsrv --recovery <action>
Date: Wed, 6 Oct 2004 11:22:41 +0100
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----=_NextPart_000_002D_01C4AB96.CB62CB30"
In-Reply-To: <pan.2004.10.06.09.57.23.578773@hochreiter.at>
Message-ID: <NUTMEG2cmbiuUNM0P2c000002a8@NUTMEG.CAM.ARTIMI.COM>
X-OriginalArrivalTime: 06 Oct 2004 10:22:41.0923 (UTC) FILETIME=[69A34530:01C4AB8E]
Note-from-DJ: This may be spam

------=_NextPart_000_002D_01C4AB96.CB62CB30
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

> -----Original Message-----
> From: cygwin-owner On Behalf Of Rainer Hochreiter
> Sent: 06 October 2004 10:57

> well, are there any guidelines how to submit patches and describing
> ChangeLog syntax available?

  Check out http://cygwin.com/contrib.html, which includes a link to
http://www.gnu.org/prep/standards_42.html for the changelog syntax.

  Oh.  I should have said "which includes a broken link.  Try

http://www.gnu.org/prep/standards/html_node/Change-Logs.html#Change-Logs 

instead".  Ping webmaster!

> > That's the change from direct writing of registry keys to using
> > that ChangeServiceConfig2 function.
> 
> right! but if using ChangeServiceConfig2() is prohibited, why 
> not writing 
> also directly to registry? 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 ;-)

  Looks to me like it's a struct _SERVICE_FAILURE_ACTIONS, with a mysterious extra
DWORD between the cActions member and the SC_ACTION array.


    cheers, 
      DaveK
-- 
Can't think of a witty .sigline today....

------=_NextPart_000_002D_01C4AB96.CB62CB30
Content-Type: application/octet-stream;
	name="contrib-patch.diff"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
	filename="contrib-patch.diff"

Index: contrib.html
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
RCS file: /cvs/cygwin/htdocs/contrib.html,v
retrieving revision 1.53
diff -p -u -r1.53 contrib.html
--- contrib.html	9 Jun 2004 02:09:36 -0000	1.53
+++ contrib.html	6 Oct 2004 10:16:47 -0000
@@ -96,7 +96,7 @@ uuencode or otherwise encrypt it.</p>
 <P>Then send it to the cygwin-patches list in an email along with an
 explanation of what the change does.  <em>Make sure that you include a Cha=
ngeLog
 entry</em>.  If you have never used a ChangeLog before 1) refer to the <a
-href=3D"http://www.gnu.org/prep/standards_42.html">GNU ChangeLog
+href=3D"http://www.gnu.org/prep/standards/html_node/Change-Logs.html#Chang=
e-Logs">GNU ChangeLog
 Standards</a> and 2) model your entry after other entries in the file
 winsup/ChangeLog.</p>
=20


------=_NextPart_000_002D_01C4AB96.CB62CB30
Content-Type: text/plain; charset=us-ascii

--
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/
------=_NextPart_000_002D_01C4AB96.CB62CB30--