{=
  include("docs.util");
  start_docs_page(docs.technical_manual.page_titles.pathnames);
=}

<p>A pathname is a value which fully describes the location of a file or $lang_stats.directory on your computer.  Pathnames are used in $PRODUCT_NAME to describe the locations of the log data, the server $lang_stats.directory, the {=docs_option_link('dd')=}, and other files and $lang_stats.directories.</p>

<p>The leftmost part of a pathname generally describes which hard drive or partition the file or $lang_stats.directory is on, and as you move from left to right along the pathname, each successive part narrows the location further by providing the name of an additional sub$(lang_stats.directory).</p>

<p>It is not generally necessary to type pathnames if you are using the $PRODUCT_NAME graphical web browser interface; the Browse button next to each pathname field provides an easier way to specify a pathname, using a familiar $lang_stats.directory browsing mechanism. This button is available everywhere except when choosing the server $lang_stats.directory in CGI mode, where you must manually enter the pathname.</p>

<p>Pathnames use different formats on different platforms. On Windows, the format is</p>

<pre>  <i>driveletter</i>:\<i>$(lang_stats.directory)1</i>\<i>$(lang_stats.directory)2</i> ... <i>$(lang_stats.directory)n</i>\<i>filename</i></pre>

<p>for files, and the same for $lang_stats.directories, except that the final <code>filename</code> is omitted (but not the final <code>\</code>).  For instance, a file <code>my.conf</code> inside the $lang_stats.directory <code>configs</code>, which is inside the $lang_stats.directory <code>$PRODUCT_EXECUTABLE_DOCS</code>, which is inside the $lang_stats.directory <code>web</code> on the C: drive, is represented by <code>C:\web\<b></b>$PRODUCT_EXECUTABLE_DOCS\configs\my.conf</code> .  The $lang_stats.directory containing <code>my.conf</code> is represented by <code>C:\web\<b></b>$PRODUCT_EXECUTABLE_DOCS\configs\</code> .</p>

<p>On MacOS X, Linux, or other UNIX-type systems, the format is</p>

<pre>  /<i>$(lang_stats.directory)1</i>/<i>$(lang_stats.directory)2</i> ... <i>$(lang_stats.directory)n</i>/<i>filename</i></pre>

<p>for files, and the same for $lang_stats.directories, except that the final <code>filename</code> is omitted (but not the final <code>/</code>).  For instance, a file <code>my.conf</code> inside the $lang_stats.directory <code>configs</code>, which is inside the $lang_stats.directory <code>$PRODUCT_EXECUTABLE_DOCS</code>, which is inside the $lang_stats.directory <code>web</code> (a sub$lang_stats.directory of the root <code>/</code> $lang_stats.directory), is represented by <code>/web/$PRODUCT_EXECUTABLE_DOCS/configs/my.conf</code> .  The $lang_stats.directory containing <code>my.conf</code> is represented by <code>/web/$PRODUCT_EXECUTABLE_DOCS/configs/</code> .<p>

{= end_docs_page() =}