This is the mail archive of the
mailing list for the Cygwin project.
Re: [PATCH] cygrunsrv --recovery <action>
- From: Corinna Vinschen <corinna-cygwin at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Wed, 6 Oct 2004 12:17:49 +0200
- Subject: Re: [PATCH] cygrunsrv --recovery <action>
- References: <firstname.lastname@example.org> <20040930153543.GC29206@cygbert.vinschen.de> <Pine.GSO.email@example.com> <20040930161545.GC26915@cygbert.vinschen.de> <firstname.lastname@example.org>
- Reply-to: cygwin at cygwin dot com
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 Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader mailto:email@example.com
Red Hat, Inc.
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html