Bug#669726: release-notes: Please document tmpfs filesystem changes for wheezy
Le Sun, Apr 07, 2013 at 09:04:16AM +0300, Andrei POPESCU a écrit :
> On Vi, 05 apr 13, 14:48:44, Julien Cristau wrote:
> >
> > Two comments:
> > - I don't think the last two sentences are particularly helpful in the
> > RN, so I'd drop them
> > - I'm confused by the bit about TMPDIR, since we don't say anything
> > about setting that variable anywhere, so even if an app obeys TMPDIR
> > if it's set, it'll still fill up /tmp by default.
>
> I'd reword it slightly:
>
> Applications which create excessively large temporary files may cause
> /tmp to run out of free space. It should possible to configure a
> different location for those files by setting the TMPDIR environment
> variable. Applications that don't honour TMPDIR and don't have any other
> means to configure the destination of temporary files require fixing.
> Please consider filing a bug report against the application in question
> if you experience such an occurrence.
Hi all,
Here is an updated patch following the above suggestion.
If the last two sentences are problematic, I think that the patch is
trivial to be edited, that is: if you decide to remove them, please
ping me if you want me to refresh the patch.
Cheers,
--
Charles Plessy
Tsurumi, Kanagawa, Japan
Index: en/whats-new.dbk
===================================================================
--- en/whats-new.dbk (révision 9738)
+++ en/whats-new.dbk (copie de travail)
@@ -689,6 +689,141 @@
</section>
+<section id="tmpfs-filesystems">
+ <title>Temporary filesystems</title>
+ <para>
+ In previous releases, temporary (<literal>tmpfs</literal>) filesystems were
+ mounted on <filename class='directory'>/lib/init/rw</filename>, <filename
+ class='directory'>/dev/shm/</filename> and optionally on <filename
+ class='directory'>/var/lock</filename> and <filename
+ class='directory'>/var/run</filename>. <filename
+ class='directory'>/lib/init/rw</filename> has been removed, and the others
+ have been moved under <filename class='directory'>/run</filename>. <filename
+ class='directory'>/var/run</filename> and <filename
+ class='directory'>/var/lock</filename> were configured using
+ <literal>RAMRUN</literal> and <literal>RAMLOCK</literal> in
+ <filename>/etc/default/rcS</filename>. All <literal>tmpfs</literal>
+ filesystems are now configurable using <filename>/etc/default/tmpfs</filename>;
+ the old settings are not migrated automatically.
+ </para>
+
+<informaltable pgwide="1">
+ <tgroup cols="4">
+ <colspec align="justify"/>
+ <colspec align="justify"/>
+ <colspec align="justify"/>
+ <colspec align="justify"/>
+ <!-- colspec align="justify" colwidth="3*"/ -->
+ <thead>
+ <row>
+ <entry>Old location</entry>
+ <entry>New location</entry>
+ <entry>Old setting</entry>
+ <entry>New setting</entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry></entry>
+ <entry></entry>
+ <entry><filename class='directory'>/etc/default/rcS</filename></entry>
+ <entry><filename class='directory'>/etc/default/tmpfs</filename></entry>
+ </row>
+ <row>
+ <entry><filename class='directory'>/lib/init/rw</filename></entry>
+ <entry><filename class='directory'>/run</filename></entry>
+ <entry>N/A</entry>
+ <entry>N/A</entry>
+ </row>
+ <row>
+ <entry><filename class='directory'>/var/run</filename></entry>
+ <entry><filename class='directory'>/run</filename></entry>
+ <entry><literal>RAMRUN</literal></entry>
+ <entry>N/A</entry>
+ </row>
+ <row>
+ <entry><filename class='directory'>/var/lock</filename></entry>
+ <entry><filename class='directory'>/run/lock</filename></entry>
+ <entry><literal>RAMLOCK</literal></entry>
+ <entry><literal>RAMLOCK</literal></entry>
+ </row>
+ <row>
+ <entry><filename class='directory'>/dev/shm</filename></entry>
+ <entry><filename class='directory'>/run/shm</filename></entry>
+ <entry>N/A</entry>
+ <entry><literal>RAMSHM</literal></entry>
+ </row>
+ <row>
+ <entry>N/A</entry>
+ <entry><filename class='directory'>/tmp</filename></entry>
+ <entry><literal></literal>N/A</entry>
+ <entry><literal>RAMTMP</literal></entry>
+ </row>
+ </tbody>
+ </tgroup>
+</informaltable>
+
+ <para>
+ The migration of data to the new locations will occur automatically during
+ the upgrade and will continue to be available at the old and new locations,
+ with the exception of <filename class='directory'>/lib/init/rw</filename>.
+ No action is required on your part, though you may wish to customise which
+ <literal>tmpfs</literal> filesystems are mounted, and their size limits, in
+ <filename>/etc/default/tmpfs</filename> after the upgrade is complete.
+ Please see the tmpfs(5) manual page for further details.
+ </para>
+
+ <para>
+ If you have written any custom scripts which make use of
+ <filename class='directory'>/lib/init/rw</filename>, these must be updated
+ to use <filename class='directory'>/run</filename> instead.
+ </para>
+
+ <para>
+ <filename class='directory'>/tmp</filename> is not a <literal>tmpfs</literal>
+ by default. If you chose to use this feature, please note that:
+ <itemizedlist>
+ <listitem>
+ <para>
+ the contents of <filename class='directory'>/tmp</filename> are not
+ preserved across reboots;
+ <filename class='directory'>/var/tmp</filename> exists for this
+ purpose;
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ the maximum size of <filename class='directory'>/tmp</filename> may
+ (depending upon your specific system) be smaller than before. If you
+ find that there is insufficient free space, it is possible to increase
+ the size limits; see tmpfs(5).
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Applications which create excessively large temporary files may cause
+ <filename class='directory'>/tmp</filename> to run out of free space.
+ It should be possible to configure a different location for those
+ files by setting the <literal>TMPDIR</literal> environment variable.
+ Applications that don't honour <literal>TMPDIR</literal> and don't
+ have any other means to configure the destination of temporary files
+ require fixing. Please consider filing a bug report against the
+ application in question if you experience such an occurrence.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ If desired, the defaults may also be overridden with an entry in in
+ <filename>/etc/fstab</filename>, for example:<programlisting>
+tmpfs /tmp tmpfs nodev,nosuid,size=20%,mode=1777 0 0
+</programlisting>
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+
</section>
+</section>
+
</chapter>
Reply to: