X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:references:in-reply-to:from:date
	:message-id:subject:to:content-type; q=dns; s=default; b=V57Wi4h
	LC08fB/MJ/MPwK7j4eJBUVLG9ocZ+2Uw5ZKo/OkX1L1CqINDHGPmJ7hWCnCNbn6Q
	CxQMr4PS7eIa93A8XeHGVfbrfp1cUbBsrZitO4VmQ0kZTCWw0uq3anDmZNKtyVrT
	+RB0gAckdIjhJPPvax5Qp1qxZGmQKlLINz2Q=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:references:in-reply-to:from:date
	:message-id:subject:to:content-type; s=default; bh=qnpwNMO3Vdf2F
	j5/MhC14tzyCtc=; b=LasT12udMrfkkQq5pkFEWbnZbe1QVOZWd2PAq+Cc4Ofdh
	YjyJukkvxWTP4aWoJmXHp4lB1KGOhuqasFORDlZUWuwK6cghvOm7ihaOIm4cHI4o
	xNnr18UEf1YlNDqgIzePfBhoZwDsV8/rZumYbqESzESCASJmDuYJQLZgf/zA/k=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
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
Authentication-Results:	sourceware.org; auth=none
X-Spam-SWARE-Status:	No, score=-1.7 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.1 spammy=
X-HELO:	mail-wm1-f49.google.com
DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=yRvXcAk38G05JHalmbxcKw37E/ihy7AS38LsHqZjT3I=; b=dEsouUEKFQvumSmT3CxbWESox/Wvd4QDnsAEogQsqkJNcvIV3JJdgiKmEnl3t3rHus jgvVJoCLH31DxGkEV1YVLXgIcmpIDcMjBvMXdeA61mjEVogWyFUiVHCJCL0Zeju6Ig5t JxulboxxqxCcFgI7ueKeqcOiim0jUYzkkMo9vhWtOJnxEcVHRBsf4G0K09tt57VopVts lhK7LSVrkSeSbS5aFyaUV1y9YTFilVI//5PbSNIGcjF2r1Ze2IGqC0Ah+ACR3eESGHRA BvzdlOYmQanr7pFa5zyS8zbiHLqj+2HXt1IhPLarMRkmCPV5e0MriCchbLPXDxuiQcfd WkmA==
MIME-Version:	1.0
References:	<BYAPR09MB29010912EBAE9D8F0196D35E9B550 AT BYAPR09MB2901 DOT namprd09 DOT prod DOT outlook DOT com> <20191212220749 DOT GB12864 AT tik DOT uni-stuttgart DOT de>
In-Reply-To:	<20191212220749.GB12864@tik.uni-stuttgart.de>
From:	Erik Soderquist <ErikSoderquist AT gmail DOT com>
Date:	Thu, 12 Dec 2019 17:45:07 -0500
Message-ID:	<CACoZoo1crFaE0ZHBVZaps+F93MyX1c4MN5-5awJ=jFmEAE2vnA@mail.gmail.com>
Subject:	Re: non-persistent storage?
To:	cygwin <cygwin AT cygwin DOT com>
X-IsSubscribed:	yes

On Thu, Dec 12, 2019 at 5:08 PM Ulli Horlacher wrote:
>
> On Thu 2019-12-12 (21:59), Buchbinder, Barry (NIH/NIAID) [E] via cygwin wrote:
>
> > If the temp file was created by mktemp and the name saved in an
> > environmental variable, each bash shell could have its own file with not
> > risk that an instance of bash would erase another instance's file.
>
> I need the opposite: all processes must read and write the same data!
> And the data must be gone when system shuts down or even if there is a
> power failure.

This is very hacky, but I believe you can get the effect you want by
having an admin process auto-start at host startup, identify itself,
and then set parts of its own /proc/ process ID tree as world
read/write.  I think this will give you the "destroyed even at power
failure" impermanence you are l,booking for.  I know it is not in the
normal layouts (like /var/run/ would be), but we are working around
limitation s imposed by Windows.

-- Erik

--
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

- Raw text -