non-persistent storage?

[Jürgen Wagner]

I can see two options:
1. You create a RAM disk and the contents will obviously be gone when 
the system reboots or crashes.
2. You encrypt the data with a ephemeral key that will be lost on reboot 
(e.g., kept in shared memory). When the system comes up and finds itself 
unable to read the data, it will erase it.

That doesn't really have much to do with Cygwin or Windows - you can do 
that on any system.

On 12.12.2019 23:07, 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.
>


-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3469 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://cygwin.com/pipermail/cygwin/attachments/20191212/d50e7176/attachment.p7s>