This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: non-persistent storage?
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@tik.uni-stuttgart.de
Allmandring 30a Tel: ++49-711-68565868
70569 Stuttgart (Germany) WWW: http://www.tik.uni-stuttgart.de/
REF:<BYAPR09MB29010912EBAE9D8F0196D35E9B550@BYAPR09MB2901.namprd09.prod.outlook.com>
--
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