From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 74465 invoked by alias); 12 Dec 2019 22:45:33 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 74328 invoked by uid 89); 12 Dec 2019 22:45:26 -0000 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 Received: from mail-wm1-f49.google.com (HELO mail-wm1-f49.google.com) (209.85.128.49) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 12 Dec 2019 22:45:24 +0000 Received: by mail-wm1-f49.google.com with SMTP id p17so4433557wmb.0 for ; Thu, 12 Dec 2019 14:45:21 -0800 (PST) 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: <20191212220749.GB12864@tik.uni-stuttgart.de> In-Reply-To: <20191212220749.GB12864@tik.uni-stuttgart.de> From: Erik Soderquist Date: Thu, 12 Dec 2019 22:57:00 -0000 Message-ID: Subject: Re: non-persistent storage? To: cygwin Content-Type: text/plain; charset="UTF-8" X-IsSubscribed: yes X-SW-Source: 2019-12/txt/msg00087.txt.bz2 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