Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!gegeweb.org!de-l.enfer-du-nord.net!feeder1.enfer-du-nord.net!feeder.erje.net!news-1.dfn.de!news.dfn.de!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: =?iso-8859-1?q?G=FCnther?= Schwarz <strap@gmx.de>
Newsgroups: comp.os.linux.security
Subject: Re: tmps and swap
Date: 7 Feb 2012 23:01:14 GMT
Lines: 19
Message-ID: <9pdopqF5ksU3@mid.individual.net>
References: <9pdh5dF5ksU1@mid.individual.net> <gwgYq.199$hJ4.174@newsfe20.iad>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-Trace: individual.net GSgIz3nRi3o9JwigQ3I2PQG4OR2s1ybh4eOtyZhFBNkZ52Kl95IqBXgiwf
Cancel-Lock: sha1:kMcjh4slpAHGn9Re3lUtsTsCbhg=
User-Agent: Pan/0.132 (Waxed in Black)
Xref: x330-a1.tempe.blueboxinc.net comp.os.linux.security:95

Lew Pitcher wrote:

> On Tuesday 07 February 2012 15:50, in comp.os.linux.security,
> strap@gmx.de wrote:
> 
>> Any hints on how to prevent a tmpfs file system to be written to the
>> swap partition? Other than omitting a swap partition completely, of
>> course. I do not want some files to end up on the hard disk.
> 
> I'm afraid that you can't do that.
> 
> To quote /usr/src/linux/Documentation/filesystems/tmpfs.txt
>   "Since tmpfs lives completely in the page cache and on swap, all tmpfs
>    pages currently in memory will show up as cached."

Thanks a lot for the clarification. So this is how I did suspect it to 
be. I will have to live with a small risk. No risk, no fun.  
 
Günther