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:date:from:to:subject:message-id:references :mime-version:content-type:in-reply-to; q=dns; s=default; b=YFlb oaTXR/vajgjzqJiJbdgWg+Nxl56WVW6NmMZhw7aNwlXGhmIbueuATaaM8QyrEh0W q9jOOsPJrfdBj3X3Nhc9b+K2mLaSpeanz6rw/EpLEln6jv4B0BnQWHlosixKpAlg UeeJALLqQbMsGmzf81D5vL3ENuMwg+MFDP83Vuk= 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:date:from:to:subject:message-id:references :mime-version:content-type:in-reply-to; s=default; bh=MDNw4k2D27 etBCYmWIT7Pn3W/8I=; b=qVAXdI1tvLX2eBA/wVKKUYCbE/DQBcU5y9l1RbNZ0h +fxusIGUITgDZSJlpfGxqI3Gpk7JazfjjzCmuyvY12A1TZ9mt2DbiqCrWnn4hHhP OYbQQLTqdMuZWJ40vOLAgTDLku8hGY68AhjazBQ/gd5MFnDFul2Bc8a44ncec8wZ s= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , 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.9 required=5.0 tests=BAYES_00 autolearn=ham version=3.3.1 spammy=tel, Tel X-HELO: smtp02.belwue.de Date: Thu, 12 Dec 2019 23:07:49 +0100 From: Ulli Horlacher To: cygwin AT cygwin DOT com Subject: Re: non-persistent storage? Message-ID: <20191212220749.GB12864@tik.uni-stuttgart.de> Mail-Followup-To: cygwin AT cygwin DOT com References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) X-IsSubscribed: yes 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. -- Ullrich Horlacher Server und Virtualisierung Rechenzentrum TIK Universitaet Stuttgart E-Mail: horlacher AT tik DOT uni-stuttgart DOT de Allmandring 30a Tel: ++49-711-68565868 70569 Stuttgart (Germany) WWW: http://www.tik.uni-stuttgart.de/ REF: -- 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