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=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
MIME-Version: 1.0
References: <BYAPR09MB29010912EBAE9D8F0196D35E9B550@BYAPR09MB2901.namprd09.prod.outlook.com> <20191212220749.GB12864@tik.uni-stuttgart.de>
In-Reply-To: <20191212220749.GB12864@tik.uni-stuttgart.de>
From: Erik Soderquist <ErikSoderquist@gmail.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@cygwin.com>
Content-Type: text/plain; charset="UTF-8"

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