[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#669726: release-notes: Please document tmpfs filesystem changes for wheezy



Le Wed, Mar 27, 2013 at 07:54:13AM +0900, Charles Plessy a écrit :
> Le Wed, Mar 27, 2013 at 01:45:35AM +0900, Osamu Aoki a écrit :
> > > 
> > > 2.2.6. Temporary filesystems
> > ...snip
> > >       * Applications which create excessively large files in /tmp may
> > >         cause /tmp to run out of free space. Such applications should not
> > >         be using /tmp, and require fixing. Please consider filing a bug
> > >         report against the application in question if you experience such
> > >         an occurrence.
> > I think above text does not account my comment:
> > * making program to honor $TMPDIR while admin set it via libpam-tmpdir 
> > 
> > This should be more like:
> > 
> > >       * Applications which create excessively large temporary files
> > >         always only in /tmp while not honoring $TMPDIR may
> > >         cause /tmp to run out of free space. Such applications should not
> > >         force to use /tmp, and require fixing. Please consider filing a bug
> > >         report against the application in question if you experience such
> > >         an occurrence.
> 
> Thanks, I will adjust the patch.

I attached an updated patch were I changed the paragraph above and also
corrected a typo where /etc/default/tmpfs was substituted by /etc/default/rcS
in the summary table.

For libpam-tmpdir, I am not able to write something by myself.  There is no
on-line documentation, and from I read in the README, I do not understand why
one would like to have /tmp on /tmpfs and then globally set TMPDIR to point to
another directory so that /tmp is not used.

Please let me know if I can help further.

Cheers,

-- 
Charles Plessy
Tsurumi, Kanagawa, Japan
Index: en/whats-new.dbk
===================================================================
--- en/whats-new.dbk	(révision 9644)
+++ en/whats-new.dbk	(copie de travail)
@@ -639,6 +639,144 @@
 
 </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;
+        </para>
+      </listitem>
+      <listitem>
+        <para>
+          <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 always
+	  only in <filename class='directory'>/tmp</filename> while not
+	  honoring <literal>TMPDIR</literal> may cause
+          <filename class='directory'>/tmp</filename> to run out of free space.
+          Such applications should not force to use
+          <filename class='directory'>/tmp</filename>, and 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: