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:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 q=dns; s=default; b=szjzyjxY6wyP88cQeJnX4Ck4RCs6VaurtJfpvfCJYDO
	7/cQxZHdlLWN7ud8Mw8FUn4vzBtiLk9kyQhPXj+F2CnLNsYISRXQHTen8fozgj7v
	skq8Bj4EHNOG2zLuLdGQrAE+27/SSeAwp5C8XJwphPXYnx0ST4ebbpoWHXhbO2oM
	=
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:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 s=default; bh=3cdeS2Rmb2Paz/ybP9jsgSM1LJY=; b=hUyah+qbxjfVS8N/V
	T98S3tyq/9exLGq64sFYlNDnDwzg0wxIAdCjbyyeQlgrYC4cgx1KFPbJc9ajmFnL
	oyWDbcZbOtTtDW6K8zNlo8uhQiAhkB8p5iaN8tz9v48TqaYiQFJ8pkRHBlI23oW+
	ENtEx7fV1lL4DoMGVqAVfUKub0=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
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=-3.2 required=5.0 tests=AWL,BAYES_00,SPF_PASS autolearn=ham version=3.3.1 spammy=100GB, 100gb, measured, communication
X-HELO: Ishtar.sc.tlinx.org
Message-ID: <5DF33CE2.8020407@tlinx.org>
Date: Thu, 12 Dec 2019 23:25:22 -0800
From: L A Walsh <cygwin AT tlinx DOT org>
User-Agent: Thunderbird
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: non-persistant storage?
References: <20191212120041 DOT GA7699 AT tik DOT uni-stuttgart DOT de> <8905c7b6-b2e6-52bf-bcdd-66890db91e9e AT cs DOT umass DOT edu> <20191212212746 DOT GA12864 AT tik DOT uni-stuttgart DOT de> <d6cd4cb8-cb75-a86d-46ac-c70f8bc73a5f AT cs DOT umass DOT edu> <5DF2E42A DOT 7020200 AT tlinx DOT org> <5a2a2640-112e-adbf-7f7a-d599b086d3cd AT SystematicSw DOT ab DOT ca>
In-Reply-To: <5a2a2640-112e-adbf-7f7a-d599b086d3cd@SystematicSw.ab.ca>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

On 2019/12/12 22:26, Brian Inglis wrote:
>
>
> I've been using /run, with /var/run as a symlink to that, created in a permanent
> postinstall script /etc/postinstall/zp_mk_run_var_links.dash (with some others),
> for some time. It's currently using ~28KB.
>
> Is it feasible to mount /run on say /dev/shm/run and create and use files there?
>   
I don't see why you would need to change what you are doing unless your 
application
whines about the symlink.  I.e. VirtualBox didn't like me using a symlink
in /opt to /home/opt on linux, so I mounted it w/a line in fstab.

/home/opt /opt  none  rbind 0 0

> Or would it be more feasible to use say Cyg/WinFUSE to provide that function?
>   
I don't know the state of cyg's support in those areas, so if you were 
forced
to change, you'd get to do your own testing to see what worked, etc.

I went one further under 'run' and 'tmp' -- I left those as public 
directories
and put my UID or login name as my own directory under the common name.

yeah 28k is nothing.  I was using files measured in MBytes though the 
[server]
system has over 100GB mem.  The communication goes through unix-sockets, 
which
also goes through /dev/shm, but its cleanup is technically the 
responsibility
of the OS, so, if lucky -- it cleans it up, if not, no worse off than 
before.

I don't run many OS progs on my Win machine cuz Win tended to flake out 
in running
tasks and wouldn't say anything when it went wrong.

So now, I just have a cronjobs on my linux server that use ssh to login 
to run
jobs on windows...

--
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