public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Michael Haubenwallner <michael.haubenwallner@ssi-schaefer.com>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] TEST: Cygwin 3.0.0-0.7
Date: Fri, 08 Feb 2019 16:35:00 -0000	[thread overview]
Message-ID: <d9e14a36-d927-6cd9-d2e8-cf1aee1ec8c9@ssi-schaefer.com> (raw)
In-Reply-To: <20190208132807.GP13951@calimero.vinschen.de>

[-- Attachment #1: Type: text/plain, Size: 231 bytes --]


On 2/8/19 2:28 PM, Corinna Vinschen wrote:
> 
> I pushed your forkable branch to master, btw.  Would you mind to do the
> honors in the ;rease notes at cygwin/release/3.0 and doc/new-features.xml?

Do you mean like this?

/haubi/

[-- Attachment #2: 0001-forkables-add-release-notes.patch --]
[-- Type: text/x-patch, Size: 2443 bytes --]

From 0461e0a552caf0c58ab7999cfd2849c7180f7d30 Mon Sep 17 00:00:00 2001
From: Michael Haubenwallner <michael.haubenwallner@ssi-schaefer.com>
Date: Fri, 8 Feb 2019 15:38:56 +0100
Subject: [PATCH] forkables: add release notes

---
 winsup/cygwin/release/3.0   | 10 ++++++++++
 winsup/doc/new-features.xml | 12 ++++++++++++
 2 files changed, 22 insertions(+)

diff --git a/winsup/cygwin/release/3.0 b/winsup/cygwin/release/3.0
index 4cd422a56..ef45e9f9d 100644
--- a/winsup/cygwin/release/3.0
+++ b/winsup/cygwin/release/3.0
@@ -66,6 +66,16 @@ What changed:
   Native Windows processes not started by Cygwin processes are mapped
   into the range beyond 65535.
 
+- Limited to executables and dlls located on the very same NTFS partition
+  as the Cygwin installation itself, and disabled by default, fork(2) now
+  is able to recover from when the executable or any dll required to load
+  into the new child process was removed or replaced since being loaded
+  into the parent process, or a dll with different content is found in the
+  parent process' current directory.  To enable this recovery feature, the
+  following command has to be executed once per Cygwin installation, with
+  subsequent shutdown of all Cygwin processes (or reboot), so the first
+  Cygwin process does find this directory existing:
+  $ mkdir --mode=a=rwxt /var/run/cygfork
 
 Bug Fixes
 ---------
diff --git a/winsup/doc/new-features.xml b/winsup/doc/new-features.xml
index 6801e3eeb..316a7446a 100644
--- a/winsup/doc/new-features.xml
+++ b/winsup/doc/new-features.xml
@@ -107,6 +107,18 @@ Native Windows processes not started by Cygwin processes are mapped
 into the range beyond 65535.
 </para></listitem>
 
+<listitem><para>
+Limited to executables and dlls located on the very same NTFS partition
+as the Cygwin installation itself, and disabled by default, fork(2) now
+is able to recover from when the executable or any dll required to load
+into the new child process was removed or replaced since being loaded
+into the parent process, or a dll with different content is found in the
+parent process' current directory.  To enable this recovery feature, the
+following command has to be executed once per Cygwin installation, with
+subsequent shutdown of all Cygwin processes (or reboot), so the first
+Cygwin process does find this directory existing:
+$ mkdir --mode=a=rwxt /var/run/cygfork
+</para></listitem>
 </itemizedlist>
 
 </sect2>
-- 
2.17.0



[-- Attachment #3: Type: text/plain, Size: 219 bytes --]


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  parent reply	other threads:[~2019-02-08 16:35 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-05 15:24 Corinna Vinschen
2019-02-07 16:14 ` Michael Haubenwallner
2019-02-07 18:27   ` Corinna Vinschen
2019-02-08  6:46     ` Michael Haubenwallner
2019-02-08 11:32       ` Corinna Vinschen
2019-02-08 11:51         ` Michael Haubenwallner
2019-02-08 12:21           ` Corinna Vinschen
2019-02-08 12:23             ` Corinna Vinschen
2019-02-08 12:52               ` Michael Haubenwallner
2019-02-08 13:06                 ` Corinna Vinschen
2019-02-08 13:28                   ` Corinna Vinschen
2019-02-08 14:43                     ` Michael Haubenwallner
2019-02-08 14:49                       ` Corinna Vinschen
2019-02-08 16:18                         ` Michael Haubenwallner
2019-02-08 16:50                           ` Corinna Vinschen
2019-02-08 16:35                     ` Michael Haubenwallner [this message]
2019-02-08 16:58                       ` Corinna Vinschen
2019-02-08 17:00                         ` Corinna Vinschen
2019-02-11 11:50                           ` Michael Haubenwallner
2019-02-11 13:33                             ` Corinna Vinschen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=d9e14a36-d927-6cd9-d2e8-cf1aee1ec8c9@ssi-schaefer.com \
    --to=michael.haubenwallner@ssi-schaefer.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).