read-only <TT
CLASS="FILENAME"
>/usr</TT
> partition, but wish to allow caching of
locally-formatted man pages. Sites that mount <TT
CLASS="FILENAME"
>/usr</TT
> as writable
(e.g., single-user installations) may choose not to use
<TT
CLASS="FILENAME"
>/var/cache/man</TT
> and may write formatted man pages into the
<TT
CLASS="FILENAME"
>cat<section></TT
> directories in <TT
CLASS="FILENAME"
>/usr/share/man</TT
> directly. We
recommend that most sites use one of the following options instead:</P
><P
></P
><UL
><LI
STYLE="list-style-type: disc"
><P
>Preformat all manual pages alongside the unformatted versions.</P
></LI
><LI
STYLE="list-style-type: disc"
><P
>Allow no caching of formatted man pages, and require formatting to be
done each time a man page is brought up.</P
></LI
><LI
STYLE="list-style-type: disc"
><P
>Allow local caching of formatted man pages in <TT
CLASS="FILENAME"
>/var/cache/man</TT
>.</P
></LI
></UL
><P
>The structure of <TT
CLASS="FILENAME"
>/var/cache/man</TT
> needs to
reflect both the fact of multiple man page hierarchies and the
possibility of multiple language support.</P
><P
>Given an unformatted manual page that normally appears in
<TT
CLASS="FILENAME"
><path>/man/<locale>/man<section></TT
>,
the directory to place formatted man pages in is
<TT
CLASS="FILENAME"
>/var/cache/man/<catpath>/<locale>/cat<section></TT
>,
where <TT
CLASS="FILENAME"
><catpath></TT
> is derived from
<TT
CLASS="FILENAME"
><path></TT
> by removing any leading
<TT
CLASS="FILENAME"
>usr</TT
> and/or trailing <TT
CLASS="FILENAME"
>share</TT
>
pathname components. (Note that the
<TT
CLASS="FILENAME"
><locale></TT
> component may be missing.)
<A
NAME="AEN2244"
HREF="#FTN.AEN2244"
><SPAN
CLASS="footnote"
>[37]</SPAN
></A
></P
><P
>Man pages written to <TT
CLASS="FILENAME"
>/var/cache/man</TT
> may
eventually be transferred to the appropriate preformatted directories
in the source <TT
CLASS="FILENAME"
>man</TT
> hierarchy or expired; likewise
formatted man pages in the source <TT
CLASS="FILENAME"
>man</TT
> hierarchy
may be expired if they are not accessed for a period of time.</P
><P
>If preformatted manual pages come with a system on read-only
media (a CD-ROM, for instance), they must be installed in the source
<TT
CLASS="FILENAME"
>man</TT
> hierarchy
(e.g. <TT
CLASS="FILENAME"
>/usr/share/man/cat<section></TT
>).
<TT
CLASS="FILENAME"
>/var/cache/man</TT
> is reserved as a writable cache
for formatted manual pages.</P
><DIV
CLASS="TIP"
><P
></P
><TABLE
CLASS="TIP"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="tip.gif"
HSPACE="5"
ALT="Tip"></TD
><TH
ALIGN="LEFT"
VALIGN="CENTER"
><B
>Rationale</B
></TH
></TR
><TR
><TD
> </TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>Release 1.2 of the standard specified
<TT
CLASS="FILENAME"
>/var/catman</TT
> for this hierarchy. The path has
been moved under <TT
CLASS="FILENAME"
>/var/cache</TT
> to better reflect the
dynamic nature of the formatted man pages. The directory name has
been changed to <TT
CLASS="FILENAME"
>man</TT
> to allow for enhancing the
hierarchy to include post-processed formats other than "cat", such as
PostScript, HTML, or DVI. </P
></TD
></TR
></TABLE
></DIV
></DIV
></DIV
></DIV
><DIV
CLASS="SECTION"
><HR><H2
CLASS="SECTION"
><A
NAME="VARCRASHSYSTEMCRASHDUMPS"
>/var/crash : System crash dumps (optional)</A
></H2
><DIV
CLASS="SECTION"
><H3
CLASS="SECTION"
><A
NAME="PURPOSE36"
>Purpose</A
></H3
><P
>This directory holds system crash dumps. As of the date of this
release of the standard, system crash dumps were not supported under
Linux but may be supported by other systems which may comply with the
FHS.</P
></DIV
></DIV
><DIV
CLASS="SECTION"
><HR><H2
CLASS="SECTION"
><A
NAME="VARGAMESVARIABLEGAMEDATA"
>/var/games : Variable game data (optional)</A
></H2
><DIV
CLASS="SECTION"
><H3
CLASS="SECTION"
><A
NAME="PURPOSE37"
>Purpose</A
></H3
><P
>Any variable data relating to games in <TT
CLASS="FILENAME"
>/usr</TT
>
should be placed here. <TT
CLASS="FILENAME"
>/var/games</TT
> should hold
the variable data previously found in <TT
CLASS="FILENAME"
>/usr</TT
>;
static data, such as help text, level descriptions, and so on, must
remain elsewhere, such as
<TT
CLASS="FILENAME"
>/usr/share/games</TT
>.</P
><DIV
CLASS="TIP"
><P
></P
><TABLE
CLASS="TIP"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="tip.gif"
HSPACE="5"
ALT="Tip"></TD
><TH
ALIGN="LEFT"
VALIGN="CENTER"
><B
>Rationale</B
></TH
></TR
><TR
><TD
> </TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
><TT
CLASS="FILENAME"
>/var/games</TT
> has been given a hierarchy of
its own, rather than leaving it merged in with the old
<TT
CLASS="FILENAME"
>/var/lib</TT
> as in release 1.2. The separation
allows local control of backup strategies, permissions, and disk
usage, as well as allowing inter-host sharing and reducing clutter in
<TT
CLASS="FILENAME"
>/var/lib</TT
>. Additionally,
<TT
CLASS="FILENAME"
>/var/games</TT
> is the path traditionally used by BSD. </P
></TD
></TR
></TABLE
></DIV
></DIV
></DIV
><DIV
CLASS="SECTION"
><HR><H2
CLASS="SECTION"
><A
NAME="VARLIBVARIABLESTATEINFORMATION"
>/var/lib : Variable state information</A
></H2
><DIV
CLASS="SECTION"
><H3
CLASS="SECTION"
><A
NAME="PURPOSE38"
>Purpose</A
></H3
><P
>This hierarchy holds state information pertaining to an
application or the system. State information is data that programs
modify while they run, and that pertains to one specific host. Users
must never need to modify files in <TT
CLASS="FILENAME"
>/var/lib</TT
> to
configure a package's operation.</P
><P
>State information is generally used to preserve the condition of
an application (or a group of inter-related applications) between
invocations and between different instances of the same application.
State information should generally remain valid after a reboot, should
not be logging output, and should not be spooled data.</P
><P
>An application (or a group of inter-related applications) must
use a subdirectory of <TT
CLASS="FILENAME"
>/var/lib</TT
> for its data.
There is one required subdirectory,