<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article PUBLIC "-//UR1//DTD docbookAllegeEsup//FR"
"http://www.esup-portail.org/consortium/espace/docbook/xxe/dtd/docbook_allege_esup.dtd">
<article lang="FR">
  <title>F.A.Q - Installation and use of the ESUP WebDAV server</title>

  <articleinfo>
    <abstract>
      <para>This document deal with the frequently asked questions ;-)</para>
    </abstract>

    <author>
      <firstname>Thomas Bellembois</firstname>

      <surname></surname>

      <affiliation>
        <orgname><ulink url="http://www.univ-rennes1.fr">University of Rennes
        1</ulink></orgname>
      </affiliation>
    </author>

    <revhistory>
      <revision>
        <revnumber>1.0</revnumber>

        <date>2006.03.03 : Thomas Bellembois (University of Rennes1)</date>

        <revdescription>
          <para>first release - Note that this page will not be versionned
          because it is often updated.</para>
        </revdescription>
      </revision>
    </revhistory>
  </articleinfo>

  <section>
    <title>Server</title>

    <section>
      <title>I can not connect to the server or the access is
      forbidden</title>

      <para>This is often because the authentication layer is not well
      configured or you are not allowed to access the resource. Configure
      carefully your <filename>build.properties</filename> file.</para>

      <para>Watch the server logs - a successfull request is like :</para>

      <para><programlisting>TP-Processor51, 03-mars-2006 11:11:48, bourges, PROPFIND, 207 "Multi-Status", 7 ms, /files/injac/res_proj_cri/</programlisting></para>

      <itemizedlist>
        <listitem>
          <para><emphasis>bourges</emphasis> is the connected user - if it is
          written <emphasis>unauthenticated</emphasis>, either you access the
          server using the unauthenticated mode or you authentication layer is
          not well configured. Note that while accessing an inJAC space the
          ESUP channel storage use a special user with root privileges.</para>
        </listitem>

        <listitem>
          <para><emphasis>PROPFIND</emphasis> is the WebDAV request</para>
        </listitem>

        <listitem>
          <para><emphasis>207</emphasis> HTTP response - it could be for
          example a 507 (quota exceeded) or 403 (forbidden) response</para>
        </listitem>

        <listitem>
          <para><emphasis>/files/injac/res_proj_cri/</emphasis> is the
          resource URI</para>
        </listitem>
      </itemizedlist>
    </section>
  </section>

  <section>
    <title>Administration tool</title>

    <section>
      <title>What about the cl parameter of the run script ?</title>

      <para>A long time ago, in a galaxy far far away, the administration
      client was designed to be run using a graphical user interface or a
      command-line mode.</para>

      <para>The G.U.I. had to be run using the <command>run.* -gr</command>
      command and the command-line mode using the <command>run.* -cl</command>
      command.</para>

      <para>But only the command-line mode is currently implemented.</para>
    </section>

    <section>
      <title>I have created homedirs but I can not access them</title>

      <para>It is often due to a wrong pattern file. You will find a good
      sample file in the user guide.</para>
    </section>
  </section>

  <section>
    <title>Miscellaneous questions</title>

    <section>
      <title>Sometimes the quota is exceeded while uploading a file ? What is
      wrong ?</title>

      <para>Nothing is wrong. The ESUP WebDAV server has a <emphasis
      role="bold">soft</emphasis> quota management system. It means that a
      quota can be exceeded <emphasis role="bold">at most 1
      time</emphasis>.</para>

      <para>The killing question is : "Why having developped such a quota
      management system ?"</para>

      <para>We did not intend to develop a soft quota management system. The
      problem is that the quota listener relies on the content-length HTTP
      header to check if a resource to put/copied/moved on the server will
      leads to an overquota. But the content-length HTTP header is optionnal
      and in this way, the listener can not check the overquota "on the fly"
      and just check if the quota was already exceeded just before the action
      in progress.</para>
    </section>

    <para> </para>
  </section>
</article>