Seconded: Russ Allbery <rra@debian.org>
Seconded: Henrique de Moraes Holschuh <hmh@debian.org>
Closes: #513955
+ * Policy: /var/run and /var/lock may be volatile
+ Wording: Colin Watson <cjwatson@debian.org>
+ Seconded: Russ Allbery <rra@debian.org>
+ Seconded: Bill Allombert <Bill.Allombert@math.u-bordeaux1.fr>
+ Closes: #514326
* Improve the documentation of maintainer script actions for diversions
in the informative appendix to allow for addition of a new diversion
on upgrade and handle error cases correctly. Thanks to Olivier Berger
script must behave sensibly and not fail if the
<file>/etc/default</file> file is deleted.
</p>
+
+ <p>
+ <file>/var/run</file> and <file>/var/lock</file> may be mounted
+ as temporary filesystems<footnote>
+ For example, using the <tt>RAMRUN</tt> and <tt>RAMLOCK</tt>
+ options in <file>/etc/default/rcS</file>.
+ </footnote>, so the <file>init.d</file> scripts must handle this
+ correctly. This will typically amount to creating any required
+ subdirectories dynamically when the <file>init.d</file> script
+ is run, rather than including them in the package and relying on
+ <prgn>dpkg</prgn> to create them.
+ </p>
</sect1>
<sect1>
arguments and supports assignment. [10.4]
* User mailboxes may be mode 600 and owned by the user rather than
mode 660, owned by user, and group mail. [11.6]
+ * /var/run and /var/lock may be mounted as temporary filesystems, and
+ init scripts must therefore create any necessary subdirectories
+ dynamically. [9.3.2]
3.8.0.0 Jun 2008