From boxbackup-dev@fluffy.co.uk  Sat Apr  1 10:37:31 2006
From: boxbackup-dev@fluffy.co.uk (Chris Wilson)
Date: Sat, 01 Apr 2006 09:37:31 +0000
Subject: [Box Backup-dev] Errors with trunk client (Win32)
In-Reply-To: <43FBA29E.3090906@hostingbrothers.nl>
References: <43FA479D.6000301@hostingbrothers.nl>
 <Pine.LNX.4.62.0602202355550.14656@top.qwarx.com>
 <43FAEFE6.4020508@hostingbrothers.nl> <43FB7785.8010104@hostingbrothers.nl>
 <Pine.LNX.4.62.0602212119310.14656@top.qwarx.com>
 <43FB909A.3020404@hostingbrothers.nl>
 <Pine.LNX.4.62.0602212243430.14656@top.qwarx.com>
 <43FBA29E.3090906@hostingbrothers.nl>
Message-ID: <1143884252.6857.28.camel@localhost>

Hi Roy,

On Wed, 2006-02-22 at 00:30 +0100, Roy wrote:

> With the new version compiled from your sources, I don't have those 
> errors thrown at me, but I still think there is something wrong.
> When I start bbackupd:
> INFO: Starting daemon (config: C:\Program Files\Box 
> Backup\bbackupd.conf) (version 0.09hWin32).
> INFO: TRACE: Set maximum diffing time to 20 seconds.
> 
> When I run bbackupquery, it shows the output pasted below in the Dos box:
> C:\Program Files\Box Backup\bbackupd>bbackupquery.exe
> Box Backup Query Tool v0.09hWin32, (c) Ben Summers and contributors 
> 2003-2006
> Using configuration file C:\Program Files\Box Backup\bbackupd.conf
> No random device -- additional seeding of random number generator not 
> performed.
> 
> Connecting to store...
> Handshake with store...
> Login to store...
> Login complete.
> 
> Type "help" for a list of commands.
> 
> query > Failed to read from console: error 8
> Exception: Common OSFileError (1/9)

I just realised that I never replied to this message. Sorry! Are you
still having the same problems?

Cheers, Chris.
-- 
  ___ __     _
 / __/ / ,__(_)_  | Chris Wilson <0000 at qwirx.com> - Cambs UK |
/ (_/ ,\/ _/ /_ \ | Security/C/C++/Java/Perl/SQL/HTML Developer |
\ _/_/_/_//_/___/ | We are GNU-free your mind-and your software |


From boxbackup-dev@fluffy.co.uk  Sat Apr  1 19:10:36 2006
From: boxbackup-dev@fluffy.co.uk (Roy)
Date: Sat, 01 Apr 2006 20:10:36 +0200
Subject: [Box Backup-dev] Errors with trunk client (Win32)
In-Reply-To: <1143884252.6857.28.camel@localhost>
References: <43FA479D.6000301@hostingbrothers.nl>	 <Pine.LNX.4.62.0602202355550.14656@top.qwarx.com>	 <43FAEFE6.4020508@hostingbrothers.nl> <43FB7785.8010104@hostingbrothers.nl>	 <Pine.LNX.4.62.0602212119310.14656@top.qwarx.com>	 <43FB909A.3020404@hostingbrothers.nl>	 <Pine.LNX.4.62.0602212243430.14656@top.qwarx.com>	 <43FBA29E.3090906@hostingbrothers.nl> <1143884252.6857.28.camel@localhost>
Message-ID: <442EC21C.9040308@hostingbrothers.nl>

Chris Wilson wrote:
> Hi Roy,
>
> On Wed, 2006-02-22 at 00:30 +0100, Roy wrote:
>
>   
>> With the new version compiled from your sources, I don't have those 
>> errors thrown at me, but I still think there is something wrong.
>> When I start bbackupd:
>> INFO: Starting daemon (config: C:\Program Files\Box 
>> Backup\bbackupd.conf) (version 0.09hWin32).
>> INFO: TRACE: Set maximum diffing time to 20 seconds.
>>
>> When I run bbackupquery, it shows the output pasted below in the Dos box:
>> C:\Program Files\Box Backup\bbackupd>bbackupquery.exe
>> Box Backup Query Tool v0.09hWin32, (c) Ben Summers and contributors 
>> 2003-2006
>> Using configuration file C:\Program Files\Box Backup\bbackupd.conf
>> No random device -- additional seeding of random number generator not 
>> performed.
>>
>> Connecting to store...
>> Handshake with store...
>> Login to store...
>> Login complete.
>>
>> Type "help" for a list of commands.
>>
>> query > Failed to read from console: error 8
>> Exception: Common OSFileError (1/9)
>>     
>
> I just realised that I never replied to this message. Sorry! Are you
> still having the same problems?
>
> Cheers, Chris.
>   
Hi Chris,

no, that problem is solved. I'm not really sure anymore what it was. But 
I thought Mark fixed this problem.

Haven't tested Box Backup for a while now, because of the last problem I 
had. I was trying to backup a directory that was too big for the store. 
So I tried to increase the size, but that failed miserably. The server 
rejected the commands I gave. Unfortunately I don't know which errors at 
the moment. But my plan is to install it on a new server and do some 
more testing there.
I have the feeling that it is not yet stable enough to deploy in a mixed 
windows / linux environment as a backup solution.

Gr.
Roy

From boxbackup-dev@fluffy.co.uk  Thu Apr  6 10:19:06 2006
From: boxbackup-dev@fluffy.co.uk (boxbackup-dev@fluffy.co.uk)
Date: Thu,  6 Apr 2006 09:19:06 +0000 (GMT)
Subject: [Box Backup-dev] COMMIT r553 - box/trunk/documentation/boxbackup
Message-ID: <20060406091906.DC1BE95@s0g0.pems.testserver.co.uk>

Author: per
Date: 2006-04-06 09:19:02 +0000 (Thu, 06 Apr 2006)
New Revision: 553

Added:
   box/trunk/documentation/boxbackup/bbackupquery.xml
Modified:
   box/trunk/documentation/boxbackup/Makefile
Log:
Added man page for bbackupquery, and updated Makefile to be able to build the man pages.


Modified: box/trunk/documentation/boxbackup/Makefile
===================================================================
--- box/trunk/documentation/boxbackup/Makefile	2006-03-31 01:14:47 UTC (rev 552)
+++ box/trunk/documentation/boxbackup/Makefile	2006-04-06 09:19:02 UTC (rev 553)
@@ -4,11 +4,11 @@
 
 DBPROC=/usr/bin/xsltproc
 BOOKXSL=bb-book.xsl
-MANXSL=bb-man.xsl
+MANXSL= /usr/share/sgml/docbook/xsl-stylesheets/manpages/docbook.xsl
 VPATH= adminguide
 .SUFFIXES: .html .xml
 
-all: adminguide instguide 
+all: adminguide instguide manpages
 
 adminguide: adminguide/index.html 
 
@@ -24,6 +24,14 @@
 ExceptionCodes.xml: ../../ExceptionCodes.txt
 	perl ./generate_except_xml.pl
 
+manpages: bbackupquery.html bbackupquery.1 
+
+bbackupquery.html: bbackupquery.xml
+	$(DBPROC) -o man-html/bbackupquery.html $(BOOKXSL) bbackupquery.xml
+
+bbackupquery.1: bbackupquery.xml
+	$(DBPROC) -o man-pages/bbackupquery.1 $(MANXSL) bbackupquery.xml
+
 dockit: instguide adminguide
 	tar zcf documentation-kit-0.10.tar.gz html/ instguide/ adminguide/
 

Added: box/trunk/documentation/boxbackup/bbackupquery.xml
===================================================================
--- box/trunk/documentation/boxbackup/bbackupquery.xml	2006-03-31 01:14:47 UTC (rev 552)
+++ box/trunk/documentation/boxbackup/bbackupquery.xml	2006-04-06 09:19:02 UTC (rev 553)
@@ -0,0 +1,349 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<refentry>
+  <refmeta>
+    <refentrytitle>bbackupquery</refentrytitle>
+
+    <manvolnum>1</manvolnum>
+  </refmeta>
+
+  <refnamediv>
+    <refname>bbackupquery</refname>
+
+    <refpurpose>Box Backup store query and retrieval</refpurpose>
+  </refnamediv>
+
+  <refsynopsisdiv>
+    <cmdsynopsis>
+      <command>bbackupquery [-q] [-c configfile] [commands ...]</command>
+    </cmdsynopsis>
+  </refsynopsisdiv>
+
+  <refsection>
+    <title>Description</title>
+
+    <para><literal>bbackupquery</literal> is the main way of interacting with
+    the backup store from a Box Backup client machine. It supports both
+    interactive and batch modes of operation.</para>
+
+    <para>It can be used to reviewing the status of a client machine's backup
+    store, getting status from the store server. The main use is to retrieve
+    files and directories when needed.</para>
+
+    <para><literal>bbackupquery</literal> supports interactive and batch modes
+    of operation. Interactive mode allows for interaction with the server much
+    like an interactive FTP client.</para>
+
+    <para>Batch mode is invoked by putting commands into the invocation of
+    bbackupquery. Example:</para>
+
+    <programlisting>bbackupquery "list home-dirs" quit</programlisting>
+
+    <para>Note that commands that contain spaces are enclosed in double
+    quotes. If the <literal>quit</literal> command is ommitted, after the
+    preceding commands are completed, <literal>bbackupquery</literal> will
+    enter interactive mode.</para>
+
+    <para><emphasis role="bold">Options</emphasis></para>
+
+    <para><emphasis>-q: Quiet. Suppresses status output while
+    running.</emphasis></para>
+
+    <para><emphasis>-c configfile: Use config file, instead of the default
+    bbackupd.conf file. Can be a relative or full path.</emphasis></para>
+
+    <refsection>
+      <title>Commands</title>
+
+      <para>The commands that can be used in <literal>bbackupquery</literal>
+      are listed below.</para>
+
+      <itemizedlist>
+        <listitem>
+          <para><literal>help</literal></para>
+
+          <para>Displays the basic help message, which gives information about
+          the commands available in bbackupquery. Use the form <literal>help
+          command</literal>, to get help on a specific command.</para>
+        </listitem>
+
+        <listitem>
+          <para><literal>quit</literal></para>
+
+          <para>End the session with the store server, and quit
+          <literal>bbackupquery</literal>.</para>
+        </listitem>
+
+        <listitem>
+          <para><literal>cd [options] &lt;directory-name&gt;</literal></para>
+
+          <para>Change directory. Options:</para>
+
+          <itemizedlist>
+            <listitem>
+              <para><literal>-d</literal> -- consider deleted directories for
+              traversal</para>
+            </listitem>
+
+            <listitem>
+              <para><literal>-o</literal> -- consider old versions of
+              directories for traversal. This option should never be useful in
+              a correctly formed store.</para>
+            </listitem>
+          </itemizedlist>
+        </listitem>
+
+        <listitem>
+          <para><literal>lcd &lt;local-directory-name&gt;</literal></para>
+
+          <para>Change directory on the client machine. To list the contents
+          of the local directory, type <literal>sh ls</literal> (on unix-like
+          machines). TODO: Does <literal>sh dir</literal> work on
+          Windows?</para>
+        </listitem>
+
+        <listitem>
+          <para><literal>list [options] [directory-name]</literal></para>
+
+          <para>The <literal>list</literal> (or its synonym
+          <literal>ls</literal>) command lists the content of the current, or
+          specified, directory. The options are as follows:</para>
+
+          <itemizedlist>
+            <listitem>
+              <para><literal>-r</literal> -- recursively list all files</para>
+            </listitem>
+
+            <listitem>
+              <para><literal>-d</literal> -- list deleted files and
+              directories</para>
+            </listitem>
+
+            <listitem>
+              <para><literal>-o</literal> -- list old versions of files and
+              directories</para>
+            </listitem>
+
+            <listitem>
+              <para><literal>-I</literal> -- don't display object IDs</para>
+            </listitem>
+
+            <listitem>
+              <para><literal>-F</literal> -- don't display flags</para>
+            </listitem>
+
+            <listitem>
+              <para><literal>-t</literal> -- show file modification time (and
+              attr mod time, if the object has attributes.</para>
+            </listitem>
+
+            <listitem>
+              <para><literal>-s</literal> -- show file size in blocks used on
+              server. Note that this is only a very approximate indication of
+              local file size.</para>
+            </listitem>
+          </itemizedlist>
+        </listitem>
+
+        <listitem>
+          <para><literal>ls [options] [directory-name]</literal></para>
+
+          <para>Synonym for <literal>list</literal>.</para>
+        </listitem>
+
+        <listitem>
+          <para><literal><literal>pwd</literal></literal></para>
+
+          <para>Print current directory, always relative to the backup store
+          root.</para>
+        </listitem>
+
+        <listitem>
+          <para><literal>sh &lt;shell command&gt;</literal></para>
+
+          <para>Everything after the sh is passed to a shell and run. All
+          output from the command is displayed in the client.</para>
+
+          <para>Example: to list the contents of the current directory on the
+          client machine type <literal>sh ls</literal>.</para>
+        </listitem>
+
+        <listitem>
+          <para><literal>compare -a</literal></para>
+
+          <para><literal>compare -l &lt;location-name&gt;</literal></para>
+
+          <para><literal>compare &lt;store-dir-name&gt;
+          &lt;local-dir-name&gt;</literal></para>
+
+          <para>Compare the current data in the store with the data on the
+          disc. Please note that all the data will be downloaded from the
+          store, so this can be a very lengthy process depending on the size
+          of the store, and the size of the part you are comparing.</para>
+
+          <para>Options:</para>
+
+          <itemizedlist>
+            <listitem>
+              <para><literal>-a</literal> -- compare all locations. </para>
+            </listitem>
+
+            <listitem>
+              <para><literal>-l</literal> -- compare one backup location as
+              specified in the configuration file. This compares one of the
+              top level store directories.</para>
+            </listitem>
+
+            <listitem>
+              <para><literal>-c</literal> -- set return code. The return code
+              is set to the following values, if <literal>quit</literal> is
+              the next command. So, if another command is run after the
+              <literal>compare</literal>, the return code will not refer to
+              the <literal>compare</literal>. This option is very useful for
+              automating compares. Return code values:</para>
+
+              <itemizedlist>
+                <listitem>
+                  <para>1 -- no differences were found</para>
+                </listitem>
+
+                <listitem>
+                  <para>2 -- differences were found</para>
+                </listitem>
+
+                <listitem>
+                  <para>3 -- an error occured</para>
+                </listitem>
+              </itemizedlist>
+            </listitem>
+          </itemizedlist>
+        </listitem>
+
+        <listitem>
+          <para><literal>get &lt;object-filename&gt;
+          [&lt;local-filename&gt;]</literal></para>
+
+          <para><literal>get -i &lt;object-id&gt;
+          &lt;local-filename&gt;</literal></para>
+
+          <para>Gets a file from the store. Object is specified as the
+          filename within the current directory. Local filename is optional.
+          Ignores old and deleted files when searching the directory for the
+          file to retrieve.</para>
+
+          <para>To get an old or deleted file, use the <literal>-i</literal>
+          option and select the object as a hex object ID (first column in
+          listing). The local filename must be specified.</para>
+        </listitem>
+
+        <listitem>
+          <para><literal>getobject &lt;object-id&gt;
+          &lt;local-filename&gt;</literal></para>
+
+          <para>Gets the object specified by the object id (in hex) and stores
+          the raw contents in the local file specified. <emphasis
+          role="bold">Note</emphasis>: This is only useful for debugging as it
+          does not decode files from the stored format, which is encrypted and
+          compressed.</para>
+        </listitem>
+
+        <listitem>
+          <para><literal>restore [-d] &lt;directory-name&gt;
+          &lt;local-directory-name&gt;</literal></para>
+
+          <para><literal>restore -r</literal></para>
+
+          <para>Restores a directory to the local disc. The local directory
+          specified must not exist (unless a previous restore is being
+          restarted). The root cannot be restored -- restore locations
+          individually. </para>
+
+          <para>Options:</para>
+
+          <itemizedlist>
+            <listitem>
+              <para><literal>-d</literal> -- restore a deleted
+              directory</para>
+            </listitem>
+
+            <listitem>
+              <para><literal>-r</literal> -- resume an interrupted
+              restore</para>
+            </listitem>
+          </itemizedlist>
+
+          <para> If a restore operation is interrupted for any reason, it can
+          be restarted using the <literal>-r</literal> switch. Restore
+          progress information is saved in a file at regular intervals during
+          the restore operation to allow restarts.</para>
+        </listitem>
+
+        <listitem>
+          <para>usage</para>
+
+          <para>Show space used on the server for this account. Display
+          fields:</para>
+
+          <itemizedlist>
+            <listitem>
+              <para><literal>Used</literal>: Total amount of space used on the
+              server</para>
+            </listitem>
+
+            <listitem>
+              <para><literal>Old files</literal>: Space used by old
+              files</para>
+            </listitem>
+
+            <listitem>
+              <para><literal>Deleted files</literal>: Space used by deleted
+              files</para>
+            </listitem>
+
+            <listitem>
+              <para><literal>Directories</literal>: Space used by the
+              directory structure</para>
+            </listitem>
+          </itemizedlist>
+
+          <para>When Used exceeds the soft limit, the server will start to
+          remove old and deleted files until the usage drops below the soft
+          limit. After a while, you should expect to see the usage stay at
+          just below the soft limit. You only need more space if the space
+          used by old and deleted files is near zero.</para>
+        </listitem>
+      </itemizedlist>
+    </refsection>
+  </refsection>
+
+  <refsection>
+    <title>Author</title>
+
+    <para>Ben Summers and contributors. For help, please go to the <ulink
+    url="http://boxbackup.hostworks.ca/">Wiki</ulink>, or subscribe to the Box
+    Backup <ulink
+    url="http://lists.warhead.org.uk/mailman/listinfo/boxbackup">mailing
+    list.</ulink></para>
+  </refsection>
+
+  <refsection>
+    <title>See Also</title>
+
+    <para>bbackupd.conf(8)</para>
+  </refsection>
+
+  <refsection>
+    <title>Files</title>
+
+    <para><literal>bbackupquery</literal> uses the Box Backup client
+    configuration file, usually located in
+    <filename>/etc/box/bbackupd.conf</filename>. On Windows this file is
+    usually located in the installation directory, and is named
+    <filename>bbackupd.conf</filename> as well.</para>
+  </refsection>
+
+  <refsection>
+    <title>Bugs</title>
+
+    <para>TODO: get known bugs for 0.10 in here.</para>
+  </refsection>
+</refentry>
\ No newline at end of file


From boxbackup-dev@fluffy.co.uk  Thu Apr  6 11:18:25 2006
From: boxbackup-dev@fluffy.co.uk (Martin Ebourne)
Date: Thu, 06 Apr 2006 11:18:25 +0100
Subject: [Box Backup-dev] COMMIT r553 -
 box/trunk/documentation/boxbackup
In-Reply-To: <20060406091906.DC1BE95@s0g0.pems.testserver.co.uk>
References: <20060406091906.DC1BE95@s0g0.pems.testserver.co.uk>
Message-ID: <20060406111825.83pcxs2w5lww0cgw@ebourne.me.uk>

subversion@fluffy.co.uk wrote:
> Added man page for bbackupquery, and updated Makefile to be able to   
> build the man pages.

Great stuff Per!

> +  <refsection>
> +    <title>Bugs</title>
> +
> +    <para>TODO: get known bugs for 0.10 in here.</para>
> +  </refsection>
> +</refentry>

I would suggest replacing that with details on how to report bugs, and  
giving a link to a page on the wiki with known bugs, or to a bug  
database when/if we have one instead. The old way of using the bug  
section in man pages is not really used so much now, and a lot of  
projects use it more as a way to involve people in the bugs process.

If there are known important bugs before release then I guess it's  
still ok to list them, but really they'd be better off fixed. :)

Cheers,

Martin.

From boxbackup-dev@fluffy.co.uk  Thu Apr  6 20:47:12 2006
From: boxbackup-dev@fluffy.co.uk (Per Thomsen)
Date: Thu, 06 Apr 2006 12:47:12 -0700
Subject: [Box Backup-dev] COMMIT r553 -	box/trunk/documentation/boxbackup
In-Reply-To: <20060406111825.83pcxs2w5lww0cgw@ebourne.me.uk>
References: <20060406091906.DC1BE95@s0g0.pems.testserver.co.uk> <20060406111825.83pcxs2w5lww0cgw@ebourne.me.uk>
Message-ID: <44357040.5040002@reedtz.com>

On 4/6/06 3:18 AM, Martin Ebourne wrote:
> [snip]
> I would suggest replacing that with details on how to report bugs, and
> giving a link to a page on the wiki with known bugs, or to a bug
> database when/if we have one instead. The old way of using the bug
> section in man pages is not really used so much now, and a lot of
> projects use it more as a way to involve people in the bugs process.
>
> If there are known important bugs before release then I guess it's
> still ok to list them, but really they'd be better off fixed. :)
Makes sense. I will put that in, instead of what's there now.

On a related note: Do we have a bug database? I seem to remember using
something that Nick hosted, but I can't find it now. Is that being used?

If not, should we use SourceForge's bug DB? I looked at it a bit, and It
will take a bit of setting up, by the project owner at SF (Ben...). Does
anyone have experience with this bugDB?

Alternatively, we could install Bugzilla somewhere (I don't mind hosting
it), and use that. I've used that in the past, and I like the way it
works. I don't think we'd need all the bells and whistles, but I think
they are relatively easy to disable/ignore.

Any thoughts?

Thanks,
Per

-- 
Per Reedtz Thomsen | Reedtz Consulting, LLC | F: 209 883 4119
V: 209 883 4102    |   pthomsen@reedtz.com  | C: 209 996 9561
GPG ID: 1209784F   |  Yahoo! Chat: pthomsen | AIM: pthomsen


From boxbackup-dev@fluffy.co.uk  Thu Apr  6 20:54:04 2006
From: boxbackup-dev@fluffy.co.uk (boxbackup-dev@fluffy.co.uk)
Date: Thu,  6 Apr 2006 19:54:04 +0000 (GMT)
Subject: [Box Backup-dev] COMMIT r554 - box/trunk/documentation/boxbackup
Message-ID: <20060406195404.B0A3495@s0g0.pems.testserver.co.uk>

Author: per
Date: 2006-04-06 19:54:02 +0000 (Thu, 06 Apr 2006)
New Revision: 554

Modified:
   box/trunk/documentation/boxbackup/bbackupquery.xml
Log:
Changed the 'Bugs' section, to include a description of how to file a bug.


Modified: box/trunk/documentation/boxbackup/bbackupquery.xml
===================================================================
--- box/trunk/documentation/boxbackup/bbackupquery.xml	2006-04-06 09:19:02 UTC (rev 553)
+++ box/trunk/documentation/boxbackup/bbackupquery.xml	2006-04-06 19:54:02 UTC (rev 554)
@@ -344,6 +344,37 @@
   <refsection>
     <title>Bugs</title>
 
-    <para>TODO: get known bugs for 0.10 in here.</para>
+    <para>If you find a bug in Box Backup, and you want to let us know about
+    it, join the <ulink
+    url="http://lists.warhead.org.uk/mailman/listinfo/boxbackup">mailing
+    list</ulink>, and send a description of the problem there.</para>
+
+    <para>To report a bug, give us at least the following information:</para>
+
+    <itemizedlist>
+      <listitem>
+        <para>The version of Box Backup you are running</para>
+      </listitem>
+
+      <listitem>
+        <para>The platform you are running on (Hardware and OS), for both
+        client and server.</para>
+      </listitem>
+
+      <listitem>
+        <para>If possible attach your config files (bbstored.conf,
+        bbackupd.conf) to the bug report.</para>
+      </listitem>
+
+      <listitem>
+        <para>Also attach any log file output that helps shed light on the
+        problem you are seeing.</para>
+      </listitem>
+
+      <listitem>
+        <para>And last but certainly not least, a description of what you are
+        seeing, in as much detail as possible.</para>
+      </listitem>
+    </itemizedlist>
   </refsection>
 </refentry>
\ No newline at end of file


From boxbackup-dev@fluffy.co.uk  Fri Apr  7 09:39:43 2006
From: boxbackup-dev@fluffy.co.uk (Chris Wilson)
Date: Fri, 07 Apr 2006 08:39:43 +0000
Subject: [Box Backup-dev] COMMIT r553
 -	box/trunk/documentation/boxbackup
In-Reply-To: <44357040.5040002@reedtz.com>
References: <20060406091906.DC1BE95@s0g0.pems.testserver.co.uk>
 <20060406111825.83pcxs2w5lww0cgw@ebourne.me.uk>
 <44357040.5040002@reedtz.com>
Message-ID: <1144399184.10334.206.camel@localhost>

Hi Per,

Great job with the documentation project! Thanks! Can we have some man
pages for bbstoreadmin when you get a chance? I can never remember how
to use it.

On Thu, 2006-04-06 at 12:47 -0700, Per Thomsen wrote:

> Alternatively, we could install Bugzilla somewhere (I don't mind hosting
> it), and use that. I've used that in the past, and I like the way it
> works. I don't think we'd need all the bells and whistles, but I think
> they are relatively easy to disable/ignore.

I'm not a huge fan of Bugzilla - I've always found it very difficult to
use, as a user. I do quite like Mantis, which is pretty simple to set up
and use.

Cheers, Chris.
-- 
  ___ __     _
 / __/ / ,__(_)_  | Chris Wilson <0000 at qwirx.com> - Cambs UK |
/ (_/ ,\/ _/ /_ \ | Security/C/C++/Java/Perl/SQL/HTML Developer |
\ _/_/_/_//_/___/ | We are GNU-free your mind-and your software |


From boxbackup-dev@fluffy.co.uk  Fri Apr  7 10:16:01 2006
From: boxbackup-dev@fluffy.co.uk (Per Thomsen)
Date: Fri, 07 Apr 2006 02:16:01 -0700
Subject: [Box Backup-dev] COMMIT r553 - box/trunk/documentation/boxbackup
In-Reply-To: <1144399184.10334.206.camel@localhost>
References: <20060406091906.DC1BE95@s0g0.pems.testserver.co.uk>	 <20060406111825.83pcxs2w5lww0cgw@ebourne.me.uk>	 <44357040.5040002@reedtz.com> <1144399184.10334.206.camel@localhost>
Message-ID: <44362DD1.1000107@reedtz.com>

On 4/7/06 1:39 AM, Chris Wilson wrote:
> Hi Per,
>
> Great job with the documentation project! Thanks! Can we have some man
> pages for bbstoreadmin when you get a chance? I can never remember how
> to use it.
>   
Do you mean bbstoreaccounts?

Here is the list of things I want to write man pages for:

    * bbstoreaccounts
    * bbstored-config
    * bbstored-certs
    * bbackupd
    * bbstored
    * bbackupctl
    * bbackupquery (done)
    * bbackupd.conf
    * bbstored.conf
    * raidfile.conf
    * accounts.txt

Anything missing?
> On Thu, 2006-04-06 at 12:47 -0700, Per Thomsen wrote:
>
>   
>> Alternatively, we could install Bugzilla somewhere (I don't mind hosting
>> it), and use that. I've used that in the past, and I like the way it
>> works. I don't think we'd need all the bells and whistles, but I think
>> they are relatively easy to disable/ignore.
>>     
>
> I'm not a huge fan of Bugzilla - I've always found it very difficult to
> use, as a user. I do quite like Mantis, which is pretty simple to set up
> and use.
OK. That's another option.

Anyone have strong opinions?

Thanks,
Per

-- 
Per Reedtz Thomsen | Reedtz Consulting, LLC | F: 209 883 4119
V: 209 883 4102    |   pthomsen@reedtz.com  | C: 209 996 9561
GPG ID: 1209784F   |  Yahoo! Chat: pthomsen | AIM: pthomsen


From boxbackup-dev@fluffy.co.uk  Fri Apr  7 10:37:55 2006
From: boxbackup-dev@fluffy.co.uk (Martin Ebourne)
Date: Fri, 07 Apr 2006 10:37:55 +0100
Subject: [Box Backup-dev] COMMIT r553 -
 box/trunk/documentation/boxbackup
In-Reply-To: <44362DD1.1000107@reedtz.com>
References: <20060406091906.DC1BE95@s0g0.pems.testserver.co.uk>
 <20060406111825.83pcxs2w5lww0cgw@ebourne.me.uk>
 <44357040.5040002@reedtz.com> <1144399184.10334.206.camel@localhost>
 <44362DD1.1000107@reedtz.com>
Message-ID: <1144402675.8351.2.camel@avenin.ebourne.me.uk>

On Fri, 2006-04-07 at 02:16 -0700, Per Thomsen wrote:
> > I'm not a huge fan of Bugzilla - I've always found it very difficult to
> > use, as a user. I do quite like Mantis, which is pretty simple to set up
> > and use.
> OK. That's another option.
> 
> Anyone have strong opinions?

Trac is one of the better systems around at the moment, and integrates
particularly well with svn. Ben did mention he was thinking of
installing it some time ago, but he's not said anything recently.

Cheers,

Martin.


From boxbackup-dev@fluffy.co.uk  Mon Apr 10 15:39:03 2006
From: boxbackup-dev@fluffy.co.uk (boxbackup-dev@fluffy.co.uk)
Date: Mon, 10 Apr 2006 14:39:03 +0000 (GMT)
Subject: [Box Backup-dev] COMMIT r555 - box/trunk/documentation/boxbackup
Message-ID: <20060410143903.88B9695@s0g0.pems.testserver.co.uk>

Author: per
Date: 2006-04-10 14:39:00 +0000 (Mon, 10 Apr 2006)
New Revision: 555

Added:
   box/trunk/documentation/boxbackup/bbackupctl.xml
Modified:
   box/trunk/documentation/boxbackup/Makefile
Log:
Added man-page for bbackupctl.

Makefile changes, to accommodate unlimited number of man-pages


Modified: box/trunk/documentation/boxbackup/Makefile
===================================================================
--- box/trunk/documentation/boxbackup/Makefile	2006-04-06 19:54:02 UTC (rev 554)
+++ box/trunk/documentation/boxbackup/Makefile	2006-04-10 14:39:00 UTC (rev 555)
@@ -4,7 +4,8 @@
 
 DBPROC=/usr/bin/xsltproc
 BOOKXSL=bb-book.xsl
-MANXSL= /usr/share/sgml/docbook/xsl-stylesheets/manpages/docbook.xsl
+NOCHUNKBOOKXSL=bb-nochunk-book.xsl
+MANXSL=bb-man.xsl
 VPATH= adminguide
 .SUFFIXES: .html .xml
 
@@ -24,25 +25,37 @@
 ExceptionCodes.xml: ../../ExceptionCodes.txt
 	perl ./generate_except_xml.pl
 
-manpages: bbackupquery.html bbackupquery.1 
+manpages: man-dirs man-nroff man-html
 
-bbackupquery.html: bbackupquery.xml
-	$(DBPROC) -o man-html/bbackupquery.html $(BOOKXSL) bbackupquery.xml
+man-dirs: man-pages/.there man-html/.there
 
-bbackupquery.1: bbackupquery.xml
-	$(DBPROC) -o man-pages/bbackupquery.1 $(MANXSL) bbackupquery.xml
+man-html/.there:
+	if [ ! -d man-html ]; then mkdir man-html; touch man-html/.there; fi
 
-dockit: instguide adminguide
-	tar zcf documentation-kit-0.10.tar.gz html/ instguide/ adminguide/
+man-pages/.there:
+	if [ ! -d man-pages ]; then mkdir man-pages; touch man-pages/.there; fi
 
-clean:
-	rm -rf ./instguide/
-	rm -rf ./adminguide/
-	rm ExceptionCodes.xml
-	rm documentation-kit-0.10.tar.gz
+man-nroff: bbackupquery.1 bbackupctl.1
 
+man-html: bbackupquery.html bbackupctl.html
 
-# %.html: %.xml
-# 	$(DBPROC) -o $@ $(BOOKXSL) $@.xml
+%.html: %.xml
+	$(DBPROC) -o $@ $(NOCHUNKBOOKXSL) $<
+	mv $@ man-html/.
 
+%.1: %.xml
+	$(DBPROC) -o $@ $(MANXSL) $<
+	mv $@ man-pages/.
 
+dockit: instguide adminguide manpages
+	tar zcf documentation-kit-0.10.tar.gz html/ instguide/ adminguide/ man-html/ man-pages
+
+clean:
+	if [ -d ./instguide ]; then rm -rf ./instguide/; fi
+	if [ -d ./adminguide ]; then rm -rf ./adminguide/; fi
+	if [ -d ./man-html ]; then rm -rf ./man-html/; fi
+	if [ -d ./man-pages ]; then  rm -rf ./man-pages/; fi
+	if [ -f ExceptionCodes.xml ]; then rm ExceptionCodes.xml; fi
+	if [ -f docuemtation-kit-0.10.tar.gz ]; then rm documentation-kit-0.10.tar.gz; fi
+
+

Added: box/trunk/documentation/boxbackup/bbackupctl.xml
===================================================================
--- box/trunk/documentation/boxbackup/bbackupctl.xml	2006-04-06 19:54:02 UTC (rev 554)
+++ box/trunk/documentation/boxbackup/bbackupctl.xml	2006-04-10 14:39:00 UTC (rev 555)
@@ -0,0 +1,147 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<refentry>
+  <refmeta>
+    <refentrytitle>bbackupctl</refentrytitle>
+
+    <manvolnum>1</manvolnum>
+  </refmeta>
+
+  <refnamediv>
+    <refname>bbackupctl</refname>
+
+    <refpurpose>Control the bbackupd daemon </refpurpose>
+  </refnamediv>
+
+  <refsynopsisdiv>
+    <cmdsynopsis>
+      <command>bbackupctl [-q] [-c config-file] command</command>
+    </cmdsynopsis>
+  </refsynopsisdiv>
+
+  <refsection>
+    <title>Description</title>
+
+    <para><literal>bbackupctl</literal> lets the user control the bbackupd
+    daemon on a client machine. The main use is to force a sync with the store
+    server. This is especially important if bbackupd(1) is configured to do
+    snapshot backups. In that case <literal>bbackupctl</literal> is the only
+    way to effect a backup.</para>
+
+    <para>Communication with the bbackupd daemon takes place over a local
+    socket. Some platforms (notably Windows) can't determine if the user
+    connecting on this socket has the correct credentials to execute the
+    commands, leaving a rather sizeable security hole open. To avoid this,
+    unset the CommandSocket parameter in <literal>bbackupd.conf</literal>(8).
+    That disables the command socket, so bbackupd is secure. This does,
+    however, render bbackupctl unusable.</para>
+
+    <refsection>
+      <title>Options</title>
+
+      <itemizedlist>
+        <listitem>
+          <para>-q -- quiet. Do not output status messages.</para>
+        </listitem>
+
+        <listitem>
+          <para>-c config_file -- Use a different config file from the default
+          one. Can be a full or a relative path.</para>
+        </listitem>
+      </itemizedlist>
+    </refsection>
+
+    <refsection>
+      <title>Commands</title>
+
+      <para>The following commands are available in bbackupctl:</para>
+
+      <itemizedlist>
+        <listitem>
+          <para><literal>terminate</literal></para>
+
+          <para>This command stops the bbackupd server. This is the equivalent
+          of killing (kill -KILL) the bbackupd process.</para>
+        </listitem>
+
+        <listitem>
+          <para><literal>reload</literal></para>
+
+          <para>Causes the bbackupd daemon to re-read all its configuration
+          files. Equivalent to kill -HUP.</para>
+        </listitem>
+
+        <listitem>
+          <para><literal>sync</literal></para>
+
+          <para>Initiates a backup to the store of whatever needs to be backed
+          up.</para>
+        </listitem>
+      </itemizedlist>
+    </refsection>
+  </refsection>
+
+  <refsection>
+    <title>Author</title>
+
+    <para>Ben Summers and contributors. For help, please go to the <ulink
+    url="http://boxbackup.hostworks.ca/">Wiki</ulink>, or subscribe to the Box
+    Backup <ulink
+    url="http://lists.warhead.org.uk/mailman/listinfo/boxbackup">mailing
+    list.</ulink></para>
+  </refsection>
+
+  <refsection>
+    <title>See Also</title>
+
+    <para><literal>bbackupd.conf(8)</literal></para>
+
+    <para>bbackupd(1)</para>
+  </refsection>
+
+  <refsection>
+    <title>Files</title>
+
+    <para><literal>bbackupctl</literal> uses the Box Backup client
+    configuration file, usually located in
+    <filename>/etc/box/bbackupd.conf</filename>. On Windows this file is
+    usually located in the installation directory, and is named
+    <filename>bbackupd.conf</filename> as well.</para>
+  </refsection>
+
+  <refsection>
+    <title>Bugs</title>
+
+    <para>If you find a bug in Box Backup, and you want to let us know about
+    it, join the <ulink
+    url="http://lists.warhead.org.uk/mailman/listinfo/boxbackup">mailing
+    list</ulink>, and send a description of the problem there.</para>
+
+    <para>To report a bug, give us at least the following information:</para>
+
+    <itemizedlist>
+      <listitem>
+        <para>The version of Box Backup you are running</para>
+      </listitem>
+
+      <listitem>
+        <para>The platform you are running on (Hardware and OS), for both
+        client and server.</para>
+      </listitem>
+
+      <listitem>
+        <para>If possible attach your config files (bbstored.conf,
+        bbackupd.conf) to the bug report.</para>
+      </listitem>
+
+      <listitem>
+        <para>Also attach any log file output that helps shed light on the
+        problem you are seeing.</para>
+      </listitem>
+
+      <listitem>
+        <para>And last but certainly not least, a description of what you are
+        seeing, in as much detail as possible.</para>
+      </listitem>
+    </itemizedlist>
+  </refsection>
+</refentry>
\ No newline at end of file


From boxbackup-dev@fluffy.co.uk  Sat Apr 15 08:44:46 2006
From: boxbackup-dev@fluffy.co.uk (boxbackup-dev@fluffy.co.uk)
Date: Sat, 15 Apr 2006 07:44:46 +0000 (GMT)
Subject: [Box Backup-dev] COMMIT r556 - in box/trunk/documentation/boxbackup: . html
Message-ID: <20060415074446.CD56C95@s0g0.pems.testserver.co.uk>

Author: per
Date: 2006-04-15 07:44:41 +0000 (Sat, 15 Apr 2006)
New Revision: 556

Added:
   box/trunk/documentation/boxbackup/bb-man.xsl
   box/trunk/documentation/boxbackup/bb-nochunk-book.xsl
   box/trunk/documentation/boxbackup/bbstoreaccounts.xml
   box/trunk/documentation/boxbackup/html/bbdoc-man.css
Modified:
   box/trunk/documentation/boxbackup/Makefile
   box/trunk/documentation/boxbackup/bb-book.xsl
Log:
Added bbstoreaccounts man page.

Added man-page specific XSL stylesheets.

Rearranged the layout of the output directories. There are now
2 output directories: 

- box-hmtl, which gets tarred up into the dockit tarball for 
  installation on a web server.
- man-pages, which contains all the .1.gz files for installation
  somewhere in $MANPATH (/usr/share/man/manX?)




Modified: box/trunk/documentation/boxbackup/Makefile
===================================================================
--- box/trunk/documentation/boxbackup/Makefile	2006-04-10 14:39:00 UTC (rev 555)
+++ box/trunk/documentation/boxbackup/Makefile	2006-04-15 07:44:41 UTC (rev 556)
@@ -6,54 +6,57 @@
 BOOKXSL=bb-book.xsl
 NOCHUNKBOOKXSL=bb-nochunk-book.xsl
 MANXSL=bb-man.xsl
+HTMLPREFIX=box-html
 VPATH= adminguide
 .SUFFIXES: .html .xml
 
-all: adminguide instguide manpages
+all: adminguide instguide manpages 
 
-adminguide: adminguide/index.html 
+adminguide: $(HTMLPREFIX)/adminguide/index.html 
 
-adminguide/index.html: adminguide.xml ExceptionCodes.xml $(BOOKXSL)
+$(HTMLPREFIX)/adminguide/index.html: adminguide.xml ExceptionCodes.xml $(BOOKXSL)
 	# docname=`echo $@ | sed -e 's/\/index.html//'`
-	$(DBPROC) -o adminguide/ $(BOOKXSL) adminguide.xml
+	$(DBPROC) -o $(HTMLPREFIX)/adminguide/ $(BOOKXSL) adminguide.xml
 
-instguide: instguide/index.html 
+instguide: $(HTMLPREFIX)/instguide/index.html 
 
-instguide/index.html: instguide.xml $(BOOKXSL)
-	$(DBPROC) -o instguide/ $(BOOKXSL) instguide.xml
+$(HTMLPREFIX)/instguide/index.html: instguide.xml $(BOOKXSL)
+	$(DBPROC) -o $(HTMLPREFIX)/instguide/ $(BOOKXSL) instguide.xml
 
 ExceptionCodes.xml: ../../ExceptionCodes.txt
 	perl ./generate_except_xml.pl
 
 manpages: man-dirs man-nroff man-html
 
-man-dirs: man-pages/.there man-html/.there
+man-dirs: man-pages/.there $(HTMLPREFIX)/man-html/.there
 
-man-html/.there:
-	if [ ! -d man-html ]; then mkdir man-html; touch man-html/.there; fi
+$(HTMLPREFIX)/man-html/.there:
+	if [ ! -d man-html ]; then mkdir -p $(HTMLPREFIX)/man-html; touch $(HTMLPREFIX)/man-html/.there; fi
 
 man-pages/.there:
 	if [ ! -d man-pages ]; then mkdir man-pages; touch man-pages/.there; fi
 
-man-nroff: bbackupquery.1 bbackupctl.1
+man-nroff: bbackupquery.1 bbackupctl.1 bbstoreaccounts.1
 
-man-html: bbackupquery.html bbackupctl.html
+man-html: bbackupquery.html bbackupctl.html bbstoreaccounts.html
 
 %.html: %.xml
 	$(DBPROC) -o $@ $(NOCHUNKBOOKXSL) $<
-	mv $@ man-html/.
+	mv $@ $(HTMLPREFIX)/man-html/.
 
 %.1: %.xml
 	$(DBPROC) -o $@ $(MANXSL) $<
 	mv $@ man-pages/.
+	gzip -f -9 man-pages/$@
 
 dockit: instguide adminguide manpages
-	tar zcf documentation-kit-0.10.tar.gz html/ instguide/ adminguide/ man-html/ man-pages
+	mkdir $(HTMLPREFIX)/images
+	cp html/images/*.png $(HTMLPREFIX)/images/.
+	cp html/*.css $(HTMLPREFIX)/.
+	tar zcf documentation-kit-0.10.tar.gz $(HTMLPREFIX)/
 
 clean:
-	if [ -d ./instguide ]; then rm -rf ./instguide/; fi
-	if [ -d ./adminguide ]; then rm -rf ./adminguide/; fi
-	if [ -d ./man-html ]; then rm -rf ./man-html/; fi
+	if [ -d ./$(HTMLPREFIX) ]; then rm -rf $(HTMLPREFIX) ; fi
 	if [ -d ./man-pages ]; then  rm -rf ./man-pages/; fi
 	if [ -f ExceptionCodes.xml ]; then rm ExceptionCodes.xml; fi
 	if [ -f docuemtation-kit-0.10.tar.gz ]; then rm documentation-kit-0.10.tar.gz; fi

Modified: box/trunk/documentation/boxbackup/bb-book.xsl
===================================================================
--- box/trunk/documentation/boxbackup/bb-book.xsl	2006-04-10 14:39:00 UTC (rev 555)
+++ box/trunk/documentation/boxbackup/bb-book.xsl	2006-04-15 07:44:41 UTC (rev 556)
@@ -4,12 +4,12 @@
 
 <xsl:import href="http://docbook.sourceforge.net/release/xsl/current/html/chunk.xsl"/> 
 
-<xsl:param name="html.stylesheet" select="'../html/bbdoc.css'"/>
+<xsl:param name="html.stylesheet" select="'../bbdoc.css'"/>
 <xsl:param name="chunk.section.depth" select="'0'"/>
 <xsl:template name="user.header.navigation">
 <div id="header">
 <div id="logo">
-<img src="../html/images/bblogo.png" alt="logo" height="65" width="331" border="0" vspace="5" align="middle" /> <img src="../html/images/stepahead.png" alt="a step ahead in data security" width="182" height="11" hspace="10" vspace="20" border="0" align="middle" /></div>
+<img src="../images/bblogo.png" alt="logo" height="65" width="331" border="0" vspace="5" align="middle" /> <img src="../images/stepahead.png" alt="a step ahead in data security" width="182" height="11" hspace="10" vspace="20" border="0" align="middle" /></div>
 </div>
 </xsl:template>
 

Added: box/trunk/documentation/boxbackup/bb-man.xsl
===================================================================
--- box/trunk/documentation/boxbackup/bb-man.xsl	2006-04-10 14:39:00 UTC (rev 555)
+++ box/trunk/documentation/boxbackup/bb-man.xsl	2006-04-15 07:44:41 UTC (rev 556)
@@ -0,0 +1,9 @@
+<?xml version='1.0'?> 
+<xsl:stylesheet  
+    xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0"> 
+
+<xsl:import href="http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl"/> 
+
+<xsl:param name="chunk.section.depth" select="'0'"/>
+
+</xsl:stylesheet>

Added: box/trunk/documentation/boxbackup/bb-nochunk-book.xsl
===================================================================
--- box/trunk/documentation/boxbackup/bb-nochunk-book.xsl	2006-04-10 14:39:00 UTC (rev 555)
+++ box/trunk/documentation/boxbackup/bb-nochunk-book.xsl	2006-04-15 07:44:41 UTC (rev 556)
@@ -0,0 +1,17 @@
+<?xml version='1.0'?> 
+<xsl:stylesheet  
+    xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0"> 
+
+<xsl:import href="http://docbook.sourceforge.net/release/xsl/current/html/docbook.xsl"/> 
+
+<xsl:param name="html.stylesheet" select="'../bbdoc-man.css'"/>
+<xsl:param name="chunk.section.depth" select="'0'"/>
+<xsl:template name="user.header.content">
+<div id="header">
+<div id="logo">
+<img src="../images/bblogo.png" alt="logo" height="65" width="331" border="0" vspace="5" align="middle" /> <img src="../images/stepahead.png" alt="a step ahead in data security" width="182" height="11" hspace="10" vspace="20" border="0" align="middle" /></div>
+</div>
+</xsl:template>
+
+
+</xsl:stylesheet>

Added: box/trunk/documentation/boxbackup/bbstoreaccounts.xml
===================================================================
--- box/trunk/documentation/boxbackup/bbstoreaccounts.xml	2006-04-10 14:39:00 UTC (rev 555)
+++ box/trunk/documentation/boxbackup/bbstoreaccounts.xml	2006-04-15 07:44:41 UTC (rev 556)
@@ -0,0 +1,290 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<refentry>
+  <refmeta>
+    <refentrytitle>bbstoreaccounts</refentrytitle>
+
+    <manvolnum>1</manvolnum>
+  </refmeta>
+
+  <refnamediv>
+    <refname>bbstoreaccounts</refname>
+
+    <refpurpose>View and change account information on the store
+    server</refpurpose>
+  </refnamediv>
+
+  <refsynopsisdiv>
+    <cmdsynopsis>
+      <command>bbstoreaccounts [-c configfile] command account_id
+      [command-specific arguments]</command>
+    </cmdsynopsis>
+  </refsynopsisdiv>
+
+  <refsection>
+    <title>Description</title>
+
+    <para><literal>bbstoreaccounts</literal> is the tool for managing accounts
+    on the store server. It can be used to view information related to
+    accounts, as well as create, change and delete accounts on the store
+    server. </para>
+
+    <para><literal>bbstoreaccounts</literal> alwas takes at least 2
+    parameters: the command name and the account ID. Some commands require
+    additional parameters, and some commands have optional parameters.</para>
+
+    <refsection>
+      <title>Options</title>
+
+      <para><literal>-c &lt;configfile&gt;</literal></para>
+
+      <para>The configfile to use for connecting to the store. Default is
+      <literal>/etc/box/bbstored.conf</literal>.</para>
+    </refsection>
+
+    <refsection>
+      <title>Commands</title>
+
+      <para>The commands tells bbstoreaccounts what action to perform.</para>
+
+      <itemizedlist>
+        <listitem>
+          <para><literal>check &lt;account-id&gt; [fix]</literal></para>
+
+          <para>The <literal>check</literal> command verifies the integrity of
+          the store account given, and optionally fixes any corruptions.
+          <emphasis role="bold">Note</emphasis>: It is recommended to run the
+          'simple' check command (without <literal>fix</literal>) before using
+          the <literal>fix</literal> option, This gives an overview of the
+          extent of any problems, before attempting to fix them.</para>
+        </listitem>
+
+        <listitem>
+          <para><literal>create &lt;account-id&gt; &lt;discset&gt;
+          &lt;softlimit&gt; &lt;hardlimit&gt;</literal></para>
+
+          <para>Creates a new store account with the parameters given. The
+          parameters are as follows:</para>
+
+          <itemizedlist>
+            <listitem>
+              <para><literal>account-id</literal>: the ID of the new account
+              to be created. A 32-bit hexadecimal number. Cannot already exist
+              on the server.</para>
+            </listitem>
+
+            <listitem>
+              <para><literal>discset</literal>: the disc set from
+              raidfile.conf(5) where the backups for this client will be
+              stored.. A number. Each RAID-file set has a number in
+              raidfile.conf. This number is what's used.</para>
+            </listitem>
+
+            <listitem>
+              <para><literal>softlimit</literal>: The soft limit is the amount
+              of storage that the server will guarantee to be available for
+              storage.</para>
+            </listitem>
+
+            <listitem>
+              <para><literal>hardlimit</literal>: The amount of storage that
+              the the server will allow, before rejecting uploads, and
+              starting to eliminate old and deleted files to get back down to
+              <literal>softlimit</literal>. </para>
+            </listitem>
+          </itemizedlist>
+        </listitem>
+
+        <listitem>
+          <para><literal>delete &lt;account-id&gt; [yes]</literal></para>
+
+          <para>Deletes the account from the store server completely. Removes
+          all backups and deletes all references to the account in the config
+          files.</para>
+
+          <para><literal>delete</literal> will ask for confirmation from the
+          user, when called. Using the <literal>yes</literal> flag, eliminates
+          that need. This is useful when deleting accounts from within a
+          script or some other automated means.</para>
+        </listitem>
+
+        <listitem>
+          <para><literal>info &lt;account-id&gt;</literal></para>
+
+          <para>Display information about the given account. Example:</para>
+
+          <programlisting> root]# bbstoreaccounts info 1
+                  Account ID: 00000001
+              Last object ID: 58757
+                 Blocks used: 9864063 (38531.50Mb)
+    Blocks used by old files: 62058 (242.41Mb)
+Blocks used by deleted files: 34025 (132.91Mb)
+  Blocks used by directories: 6679 (26.09Mb)
+            Block soft limit: 11796480 (46080.00Mb)
+            Block hard limit: 13107200 (51200.00Mb)
+         Client store marker: 1139559852000000 </programlisting>
+
+          <para>Explanation:</para>
+
+          <itemizedlist>
+            <listitem>
+              <para>Account ID: The account ID being displayed.</para>
+            </listitem>
+
+            <listitem>
+              <para>Last Object ID: A counter that keeps track of the objects
+              that have been backed up. This number refers to the last file
+              that was written to the store. The ID is displayed as a decimal
+              number, and the object ID can be converted to a path name to a
+              file as follows: convert the number to hex (e.g.: 58757 =&gt;
+              0xE585); The last backed up file will be (relative from the
+              client's store root): <literal>e5/o85.rfw</literal>. Longer
+              numbers infer more directories in the structure, so as an
+              example 3952697264 as the last object ID gives 0xEB995FB0, which
+              translates to a backup pathname of
+              <literal>0e/b9/95/f0/b0.rfw.</literal></para>
+            </listitem>
+
+            <listitem>
+              <para>Blocks used: The number of blocks used by the store. The
+              size in Mb depends on the number of blocks, as well as the block
+              size for the disc set given in
+              <literal>raidfile.conf(5)</literal>. In this case the block size
+              is 4096.</para>
+            </listitem>
+
+            <listitem>
+              <para>Blocks used by old files: The number of blocks occupied by
+              files that have newer versions in the store. This data is at
+              risk for being removed during housekeeping.</para>
+            </listitem>
+
+            <listitem>
+              <para>Blocks used by deleted files: The number of blocks used by
+              files that have been deleted on the client. This data is at risk
+              for being removed during housekeeping.</para>
+            </listitem>
+
+            <listitem>
+              <para>Blocks used by directories: The number of blocks used by
+              directories in the store.</para>
+            </listitem>
+
+            <listitem>
+              <para>Block soft limit: The soft limit in blocks. The soft limit
+              is the maximum guaranteed storage space available to the
+              account. When housekeeping starts, and the old and deleted files
+              are removed, they are removed in chronological order (oldest
+              first), until the data used is less than the soft limit.</para>
+            </listitem>
+
+            <listitem>
+              <para>Block hard limit: The hard limit in blocks. The hard limit
+              is the most amount of storage the server will allow in an
+              account. Any data above this amount will be rejected.
+              Housekeeping will reduce the storage use, so more data can be
+              uploaded.</para>
+            </listitem>
+
+            <listitem>
+              <para>Client store marker: TODO What exactly is this? </para>
+            </listitem>
+          </itemizedlist>
+        </listitem>
+
+        <listitem>
+          <para><literal>setlimit &lt;account-id&gt; &lt;softlimit&gt;
+          &lt;hardlimit&gt;</literal></para>
+
+          <para>Changes the storage space allocation for the given account. No
+          server restart is needed.</para>
+
+          <para>Parameters:</para>
+
+          <itemizedlist>
+            <listitem>
+              <para><literal>account-id</literal>: the ID of the new account
+              to be created. A 32-bit hexadecimal number. Cannot already exist
+              on the server.</para>
+            </listitem>
+
+            <listitem>
+              <para><literal>softlimit</literal>: The soft limit is the amount
+              of storage that the server will guarantee to be available for
+              storage.</para>
+            </listitem>
+
+            <listitem>
+              <para><literal>hardlimit</literal>: The amount of storage that
+              the the server will allow, before rejecting uploads, and
+              starting to eliminate old and deleted files to get back down to
+              <literal>softlimit</literal>.</para>
+            </listitem>
+          </itemizedlist>
+        </listitem>
+      </itemizedlist>
+    </refsection>
+  </refsection>
+
+  <refsection>
+    <title>Author</title>
+
+    <para>Ben Summers and contributors. For help, please go to the <ulink
+    url="http://boxbackup.hostworks.ca/">Wiki</ulink>, or subscribe to the Box
+    Backup <ulink
+    url="http://lists.warhead.org.uk/mailman/listinfo/boxbackup">mailing
+    list.</ulink></para>
+  </refsection>
+
+  <refsection>
+    <title>See Also</title>
+
+    <para><literal>bbstored.conf(5)</literal></para>
+
+    <para><literal>raidfile.conf(5)</literal></para>
+  </refsection>
+
+  <refsection>
+    <title>Files</title>
+
+    <para><literal>bbstoreaccounts</literal> uses the Box Backup server
+    configuration file, usually located in
+    <filename>/etc/box/bbstored.conf</filename>. </para>
+  </refsection>
+
+  <refsection>
+    <title>Bugs</title>
+
+    <para>If you find a bug in Box Backup, and you want to let us know about
+    it, join the <ulink
+    url="http://lists.warhead.org.uk/mailman/listinfo/boxbackup">mailing
+    list</ulink>, and send a description of the problem there.</para>
+
+    <para>To report a bug, give us at least the following information:</para>
+
+    <itemizedlist>
+      <listitem>
+        <para>The version of Box Backup you are running</para>
+      </listitem>
+
+      <listitem>
+        <para>The platform you are running on (Hardware and OS), for both
+        client and server.</para>
+      </listitem>
+
+      <listitem>
+        <para>If possible attach your config files (bbstored.conf,
+        bbackupd.conf) to the bug report.</para>
+      </listitem>
+
+      <listitem>
+        <para>Also attach any log file output that helps shed light on the
+        problem you are seeing.</para>
+      </listitem>
+
+      <listitem>
+        <para>And last but certainly not least, a description of what you are
+        seeing, in as much detail as possible.</para>
+      </listitem>
+    </itemizedlist>
+  </refsection>
+</refentry>
\ No newline at end of file

Added: box/trunk/documentation/boxbackup/html/bbdoc-man.css
===================================================================
--- box/trunk/documentation/boxbackup/html/bbdoc-man.css	2006-04-10 14:39:00 UTC (rev 555)
+++ box/trunk/documentation/boxbackup/html/bbdoc-man.css	2006-04-15 07:44:41 UTC (rev 556)
@@ -0,0 +1,104 @@
+body {
+	font-family: Verdana, Geneva, Arial, sans-serif;
+	background-color: #edeef3;
+        font-size: .75em;
+        line-height: 180%;
+        text-align: left;
+        margin-top: 20px;
+        margin-right: 100px;
+        margin-left: 250px;
+        position: relative;
+        width: auto; }
+	
+table {
+	font-family: Verdana, Geneva, Arial, sans-serif;
+	background-color: #edeef3;
+        font-size: 10pt;
+        line-height: 100%; }
+
+
+code {
+	font-size: 11pt; }
+
+	
+
+div.navheader {
+	font-family: Verdana, Geneva, Arial, sans-serif;
+	background-color: #edeef3; 
+        line-height: 100%; }
+       
+#header {
+	background-color: #e4e6ed;
+	text-align: left;
+	padding-top: 10px;
+        margin-right: -100px;
+        margin-left: -250px;
+	top: 20px;
+	border-top: 1px solid #c4c4d5;
+	border-bottom: 1px solid white }
+	
+#logo {
+	position: relative; 
+	margin-left: 200px }
+	
+	
+#page {
+	font-size: .75em;
+	line-height: 180%;
+	text-align: left;
+	margin-top: 50px;
+	margin-right: 100px;
+	margin-left: 250px;
+	position: relative;
+	width: auto }
+
+#disc {    }
+	
+.informaltable td,tr {font-size: 1em;
+	line-height: 140%;
+	text-align: left;
+	background-color: #e4e6ed;
+	padding: 4px }
+	
+tr,td {font-size: 1em;
+	line-height: 100%;
+	background-color: #edeef3; }
+	
+pre, tt { font-size: 1.3em; 
+	color: #088;
+	letter-spacing: 1px;
+	word-spacing: 2px}
+	
+h1 {
+	color: #c00;
+	font-size: 16pt;
+	margin-bottom: 2em;
+	margin-left: -50px }
+	
+h2 {
+	color: #324e95;
+	font-size: 12pt;
+	margin-top: 2em;
+	margin-left: -50px }
+	
+h3 {
+	color: #324e95;
+	font-size: 10pt;
+	margin-top: 2em;
+	margin-left: -50px }
+	
+dt { font-weight: bold }
+	
+a:link {
+	color: #324e95;
+	text-decoration: none;
+	background-color: transparent }
+	
+a:visited {
+	color: #90c;
+	text-decoration: none }
+	
+a:hover {
+	color: #c00;
+	text-decoration: underline;
+	background-color: transparent }


From boxbackup-dev@fluffy.co.uk  Sat Apr 15 09:15:36 2006
From: boxbackup-dev@fluffy.co.uk (boxbackup-dev@fluffy.co.uk)
Date: Sat, 15 Apr 2006 08:15:36 +0000 (GMT)
Subject: [Box Backup-dev] COMMIT r557 - box/trunk/documentation/boxbackup
Message-ID: <20060415081536.0953195@s0g0.pems.testserver.co.uk>

Author: per
Date: 2006-04-15 08:15:33 +0000 (Sat, 15 Apr 2006)
New Revision: 557

Modified:
   box/trunk/documentation/boxbackup/Makefile
Log:
Fixed typo in 'clean' target. dockit tarball will now be deleted.


Modified: box/trunk/documentation/boxbackup/Makefile
===================================================================
--- box/trunk/documentation/boxbackup/Makefile	2006-04-15 07:44:41 UTC (rev 556)
+++ box/trunk/documentation/boxbackup/Makefile	2006-04-15 08:15:33 UTC (rev 557)
@@ -59,6 +59,6 @@
 	if [ -d ./$(HTMLPREFIX) ]; then rm -rf $(HTMLPREFIX) ; fi
 	if [ -d ./man-pages ]; then  rm -rf ./man-pages/; fi
 	if [ -f ExceptionCodes.xml ]; then rm ExceptionCodes.xml; fi
-	if [ -f docuemtation-kit-0.10.tar.gz ]; then rm documentation-kit-0.10.tar.gz; fi
+	if [ -f documentation-kit-0.10.tar.gz ]; then rm documentation-kit-0.10.tar.gz; fi
 
 


From boxbackup-dev@fluffy.co.uk  Sat Apr 15 09:32:52 2006
From: boxbackup-dev@fluffy.co.uk (Per Thomsen)
Date: Sat, 15 Apr 2006 01:32:52 -0700
Subject: [Box Backup-dev] [Doc] A few more things to look at...
Message-ID: <4440AFB4.8090007@reedtz.com>

All,
I have put the current pages up on my web site:

    * http://www.reedtz.com/box-html/adminguide/
    * http://www.reedtz.com/box-html/instguide/
    * http://www.reedtz.com/man-html/bbackupctl.html
    * http://www.reedtz.com/man-html/bbackupquery.html
    * http://www.reedtz.com/man-html/bbstoreaccounts.html

Please let me know if you have any comments on the
layout/content/whatever. If anyone is interested in the nroff-formatted
man-pages, let me know, and I can post them, or put them up for download.

Hopefully I will be able to get to a few more man-pages written in the
next week, so we'll have a baseline doc-set.

Thanks,
Per

-- 
Per Reedtz Thomsen | Reedtz Consulting, LLC | F: 209 883 4119
V: 209 883 4102    |   pthomsen@reedtz.com  | C: 209 996 9561
GPG ID: 1209784F   |  Yahoo! Chat: pthomsen | AIM: pthomsen


From boxbackup-dev@fluffy.co.uk  Sat Apr 15 09:36:02 2006
From: boxbackup-dev@fluffy.co.uk (Per Thomsen)
Date: Sat, 15 Apr 2006 01:36:02 -0700
Subject: [Box Backup-dev] [Doc] A few more things to look at...
In-Reply-To: <4440AFB4.8090007@reedtz.com>
References: <4440AFB4.8090007@reedtz.com>
Message-ID: <4440B072.4060306@reedtz.com>

On 4/15/06 1:32 AM, Per Thomsen wrote:
> All,
> I have put the current pages up on my web site:
>
>   
Ugh!

This should teach me not to type URLs without checking all of them.

Here are the mistyped ones:

    *

      http://www.reedtz.com/box-html/man-html/bbackupctl.html

    *

      http://www.reedtz.com/box-html/man-html/bbackupquery.html

    *

      http://www.reedtz.com/box-html/man-html/bbstoreaccounts.html

Thanks,
Per

-- 
Per Reedtz Thomsen | Reedtz Consulting, LLC | F: 209 883 4119
V: 209 883 4102    |   pthomsen@reedtz.com  | C: 209 996 9561
GPG ID: 1209784F   |  Yahoo! Chat: pthomsen | AIM: pthomsen


From boxbackup-dev@fluffy.co.uk  Wed Apr 19 08:35:06 2006
From: boxbackup-dev@fluffy.co.uk (Per Thomsen)
Date: Wed, 19 Apr 2006 00:35:06 -0700
Subject: [Box Backup-dev] Userland RAID question
Message-ID: <4445E82A.70208@reedtz.com>

All,
I'm working on the docs a bit more, and I have a quick question about
the userland RAID: What RAID-level is implemented? I think it's RAID5,
but I don't know. Wanted to put a bit of background into the
raidfile-config and raidfile.conf man pages.

TIA,
Per

-- 
Per Reedtz Thomsen | Reedtz Consulting, LLC | F: 209 883 4119
V: 209 883 4102    |   pthomsen@reedtz.com  | C: 209 996 9561
GPG ID: 1209784F   |  Yahoo! Chat: pthomsen | AIM: pthomsen


From boxbackup-dev@fluffy.co.uk  Thu Apr 20 16:44:40 2006
From: boxbackup-dev@fluffy.co.uk (Stefan Norlin)
Date: Thu, 20 Apr 2006 17:44:40 +0200
Subject: [Box Backup-dev] BoxBackup on AIX 5.3
Message-ID: <066201c66491$5659f790$1601060a@cs>

This is a multi-part message in MIME format.

------=_NextPart_000_065F_01C664A2.19CD43C0
Content-Type: text/plain;
	format=flowed;
	charset="iso-8859-15";
	reply-type=original
Content-Transfer-Encoding: 7bit

Hi,

I have tried to compile BoxBackup on AIX 5.3.

A few things:

* You should always set CONFIG_SHELL as per below on
AIX, otherwise configure runs VERY slowly

CONFIG_SHELL=/opt/freeware/bin/bash
export CONFIG_SHELL

* Detection of GNU make in the should probably be done some
other way. I only modified infrastructure/BoxPlatform.pm.in as
per the attached "svn diff".

* Added AC_SEARCH_LIBS([pthread_cond_init], [pthread])
as per the attached "svn diff".

* I had to use PLATFORM_CLIB_FNS_INTERCEPTION_IMPOSSIBLE
as per the attached "svn diff".

* /opt/freeware/bin/install should be used instead of /usr/bin/install
in the parcels/scripts/install-backup-* scripts. Otherwise nothing
will be installed... :)

Could maybe be "solved" by setting PATH=/opt/freeware/bin:$PATH
in the script. A good idea anyway on AIX since all "working" binaries
are actually located there first hand. :)

* For some reason some header files only works if one disable
large file support. Other persons has run across this as well:

http://groups.google.com/group/comp.databases.berkeley-db/browse_thread/thread/d1daf868181733b8/3473aad40f3d8df2%233473aad40f3d8df2

The result from this adventure was that bbackupd does not start
due to it cannot the config file... the "bbackupquery" command
connects to the server, "usage" works, but "ls" causes an
exception to be thrown.

To be continued...

Regards,
Stefan 

------=_NextPart_000_065F_01C664A2.19CD43C0
Content-Type: text/plain;
	format=flowed;
	name="aix5-svn-diff.txt";
	reply-type=original
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
	filename="aix5-svn-diff.txt"

Index: infrastructure/BoxPlatform.pm.in=0A=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=0A=
--- infrastructure/BoxPlatform.pm.in	(revision 555)=0A=
+++ infrastructure/BoxPlatform.pm.in	(working copy)=0A=
@@ -17,7 +17,7 @@=0A=
 	$build_os =3D 'CYGWIN' if $build_os =3D~ m/CYGWIN/;=0A=
 =0A=
 	$make_command =3D ($build_os eq 'Darwin') ? 'bsdmake' : ($build_os eq =
'SunOS') ? 'gmake' : 'make';=0A=
-	$bsd_make =3D ($build_os ne 'Linux' && $build_os ne 'CYGWIN' && =
$build_os ne "SunOS");=0A=
+	$bsd_make =3D ($build_os ne 'AIX' && $build_os ne 'Linux' && $build_os =
ne 'CYGWIN' && $build_os ne "SunOS");=0A=
 =0A=
 	# blank extra flags by default=0A=
 	$platform_compile_line_extra =3D '@CPPFLAGS@ @CXXFLAGS@ =
@CXXFLAGS_STRICT@';=0A=
Index: configure.ac=0A=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=0A=
--- configure.ac	(revision 555)=0A=
+++ configure.ac	(working copy)=0A=
@@ -43,6 +43,8 @@=0A=
 AC_CHECK_LIB([z], [zlibVersion],, [AC_MSG_ERROR([[cannot find zlib]])])=0A=
 VL_LIB_READLINE([have_libreadline=3Dyes], [have_libreadline=3Dno])=0A=
 =0A=
+AC_SEARCH_LIBS([pthread_cond_init], [pthread])=0A=
+=0A=
 ## Check for Berkely DB. Restrict to certain versions=0A=
 AX_PATH_BDB(, [=0A=
   LIBS=3D"$BDB_LIBS $LIBS"=0A=
Index: lib/common/BoxPlatform.h=0A=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=0A=
--- lib/common/BoxPlatform.h	(revision 555)=0A=
+++ lib/common/BoxPlatform.h	(working copy)=0A=
@@ -46,6 +46,11 @@=0A=
 	#define PLATFORM_CLIB_FNS_INTERCEPTION_IMPOSSIBLE=0A=
 #endif=0A=
 =0A=
+// On AIX too...=0A=
+#ifdef AIX=0A=
+#define PLATFORM_CLIB_FNS_INTERCEPTION_IMPOSSIBLE=0A=
+#endif=0A=
+=0A=
 // Disable memory testing under Darwin, it just doesn't like it very =
much.=0A=
 #ifdef __APPLE__=0A=
 	// TODO: We really should get some decent leak detection code.=0A=

------=_NextPart_000_065F_01C664A2.19CD43C0--


From boxbackup-dev@fluffy.co.uk  Thu Apr 20 17:12:28 2006
From: boxbackup-dev@fluffy.co.uk (Martin Ebourne)
Date: Thu, 20 Apr 2006 17:12:28 +0100
Subject: [Box Backup-dev] BoxBackup on AIX 5.3
In-Reply-To: <066201c66491$5659f790$1601060a@cs>
References: <066201c66491$5659f790$1601060a@cs>
Message-ID: <20060420171228.90sdr532dcwcc0c8@ebourne.me.uk>

Stefan Norlin <stefan.norlin@infoflexconnect.se> wrote:
> * Detection of GNU make in the should probably be done some
> other way. I only modified infrastructure/BoxPlatform.pm.in as
> per the attached "svn diff".

Yes, that should be autoconfed properly.

> * Added AC_SEARCH_LIBS([pthread_cond_init], [pthread])
> as per the attached "svn diff".

Box doesn't use threads. Why do you need libpthread?

> * I had to use PLATFORM_CLIB_FNS_INTERCEPTION_IMPOSSIBLE
> as per the attached "svn diff".

This section needs some tlc. The whole interception thing just doesn't =20
work very reliably, but noone has come up with anything better yet.

> * You should always set CONFIG_SHELL as per below on
> AIX, otherwise configure runs VERY slowly
> * /opt/freeware/bin/install should be used instead of /usr/bin/install
> in the parcels/scripts/install-backup-* scripts. Otherwise nothing
> will be installed... :)

Presumably these two are fairly common issues when compiling external source=
?

> Could maybe be "solved" by setting PATH=3D/opt/freeware/bin:$PATH
> in the script. A good idea anyway on AIX since all "working" binaries
> are actually located there first hand. :)

Is that workaround needed for other packages? I this something that =20
can reasonably be in the install documentation?

> * For some reason some header files only works if one disable
> large file support. Other persons has run across this as well:
> http://groups.google.com/group/comp.databases.berkeley-db/browse_thread/th=
read/d1daf868181733b8/3473aad40f3d8df2%233473aad40f3d8df2

Can't remember if we've got a --disable-large-file option. We can add =20
one if not.

> The result from this adventure was that bbackupd does not start
> due to it cannot the config file... the "bbackupquery" command
> connects to the server, "usage" works, but "ls" causes an
> exception to be thrown.

Good luck!

Martin.

From boxbackup-dev@fluffy.co.uk  Thu Apr 20 17:56:38 2006
From: boxbackup-dev@fluffy.co.uk (Stefan Norlin)
Date: Thu, 20 Apr 2006 18:56:38 +0200
Subject: [Box Backup-dev] BoxBackup on AIX 5.3
References: <066201c66491$5659f790$1601060a@cs> <20060420171228.90sdr532dcwcc0c8@ebourne.me.uk>
Message-ID: <002701c6649b$63b7dba0$0101050a@stenorhem>

>> * Detection of GNU make in the should probably be done some
>> other way. I only modified infrastructure/BoxPlatform.pm.in as
>> per the attached "svn diff".
>
> Yes, that should be autoconfed properly.

Any idea how? :)

>> * Added AC_SEARCH_LIBS([pthread_cond_init], [pthread])
>> as per the attached "svn diff".
>
> Box doesn't use threads. Why do you need libpthread?

BDB wanted it, I think. It can probably be recompiled without thread 
support.

>> * You should always set CONFIG_SHELL as per below on
>> AIX, otherwise configure runs VERY slowly
>> * /opt/freeware/bin/install should be used instead of /usr/bin/install
>> in the parcels/scripts/install-backup-* scripts. Otherwise nothing
>> will be installed... :)
>
> Presumably these two are fairly common issues when compiling external 
> source?

Yep.

>> Could maybe be "solved" by setting PATH=/opt/freeware/bin:$PATH
>> in the script. A good idea anyway on AIX since all "working" binaries
>> are actually located there first hand. :)
>
> Is that workaround needed for other packages? I this something that  can 
> reasonably be in the install documentation?

Well... if you fiddle around with GNU and open source stuff you
really want it like that. (But on the other hand you should avoid AIX
entirely, if possible, for open source stuff) *grin*

>> * For some reason some header files only works if one disable
>> large file support. Other persons has run across this as well:
>> http://groups.google.com/group/comp.databases.berkeley-db/browse_thread/thread/d1daf868181733b8/3473aad40f3d8df2%233473aad40f3d8df2
>
> Can't remember if we've got a --disable-large-file option. We can add  one 
> if not.

There is one and it compiles when I use it... would be good to be able
to enable it again though. Will see what can be done.

>
> Good luck!

Much needed... thanks! 8-D


From boxbackup-dev@fluffy.co.uk  Fri Apr 21 06:24:55 2006
From: boxbackup-dev@fluffy.co.uk (Per Thomsen)
Date: Thu, 20 Apr 2006 22:24:55 -0700
Subject: [Box Backup-dev] Userland RAID question
In-Reply-To: <4445E82A.70208@reedtz.com>
References: <4445E82A.70208@reedtz.com>
Message-ID: <44486CA7.9040504@reedtz.com>

On 4/19/06 12:35 AM, Per Thomsen wrote:
> All,
> I'm working on the docs a bit more, and I have a quick question about
> the userland RAID: What RAID-level is implemented? I think it's RAID5,
> but I don't know. Wanted to put a bit of background into the
> raidfile-config and raidfile.conf man pages.
>   
Uh, anyone know this? I could start scouring the sources, but if someone
knows, that would be faster...

Thanks,
Per

-- 
Per Reedtz Thomsen | Reedtz Consulting, LLC | F: 209 883 4119
V: 209 883 4102    |   pthomsen@reedtz.com  | C: 209 996 9561
GPG ID: 1209784F   |  Yahoo! Chat: pthomsen | AIM: pthomsen


From boxbackup-dev@fluffy.co.uk  Fri Apr 21 08:55:22 2006
From: boxbackup-dev@fluffy.co.uk (Martin Ebourne)
Date: Fri, 21 Apr 2006 08:55:22 +0100
Subject: [Box Backup-dev] Userland RAID question
In-Reply-To: <44486CA7.9040504@reedtz.com>
References: <4445E82A.70208@reedtz.com>  <44486CA7.9040504@reedtz.com>
Message-ID: <1145606122.27607.5.camel@avenin.ebourne.me.uk>

On Thu, 2006-04-20 at 22:24 -0700, Per Thomsen wrote:
> On 4/19/06 12:35 AM, Per Thomsen wrote:
> > All,
> > I'm working on the docs a bit more, and I have a quick question about
> > the userland RAID: What RAID-level is implemented? I think it's RAID5,
> > but I don't know. Wanted to put a bit of background into the
> > raidfile-config and raidfile.conf man pages.
> >   
> Uh, anyone know this? I could start scouring the sources, but if someone
> knows, that would be faster...

RAID5 is correct. It's a slightly restricted RAID5 where you have to
have exactly 3 disks, rather than the more general RAID5 where you can
have n disks (n>2) and get data storage on n-1 of those (the last disk
is always the parity disk in RAID5).

Cheers,

Martin.


From boxbackup-dev@fluffy.co.uk  Fri Apr 21 10:39:31 2006
From: boxbackup-dev@fluffy.co.uk (Chris Wilson)
Date: Fri, 21 Apr 2006 09:39:31 +0000
Subject: [Box Backup-dev] Userland RAID question
In-Reply-To: <1145606122.27607.5.camel@avenin.ebourne.me.uk>
References: <4445E82A.70208@reedtz.com>  <44486CA7.9040504@reedtz.com>
 <1145606122.27607.5.camel@avenin.ebourne.me.uk>
Message-ID: <1145612371.24389.4.camel@localhost>

Hi Martin,

On Fri, 2006-04-21 at 08:55 +0100, Martin Ebourne wrote:

> (the last disk is always the parity disk in RAID5).

Maybe I'm splitting hairs, but I don't think that's strictly true. The
parity in RAID 5 is divided between all the disks in a round-robin
fashion, to avoid one disk becoming the bottleneck for all writes. I
think that RAID 4 is where one disk holds all the parity.
[http://en.wikipedia.org/wiki/RAID5#RAID_5]

Nevertheless, the total capacity of the array is the same in both cases,
which is the sum of the sizes of n-1 disks.

Cheers, Chris.
-- 
  ___ __     _
 / __/ / ,__(_)_  | Chris Wilson <0000 at qwirx.com> - Cambs UK |
/ (_/ ,\/ _/ /_ \ | Security/C/C++/Java/Perl/SQL/HTML Developer |
\ _/_/_/_//_/___/ | We are GNU-free your mind-and your software |


From boxbackup-dev@fluffy.co.uk  Fri Apr 21 10:48:46 2006
From: boxbackup-dev@fluffy.co.uk (Martin Ebourne)
Date: Fri, 21 Apr 2006 10:48:46 +0100
Subject: [Box Backup-dev] Userland RAID question
In-Reply-To: <1145612371.24389.4.camel@localhost>
References: <4445E82A.70208@reedtz.com> <44486CA7.9040504@reedtz.com>
 <1145606122.27607.5.camel@avenin.ebourne.me.uk>
 <1145612371.24389.4.camel@localhost>
Message-ID: <20060421104846.3ydqcwa30ocsgskg@ebourne.me.uk>

Chris Wilson <chris@qwirx.com> wrote:
> On Fri, 2006-04-21 at 08:55 +0100, Martin Ebourne wrote:
>> (the last disk is always the parity disk in RAID5).
>
> Maybe I'm splitting hairs, but I don't think that's strictly true. The
> parity in RAID 5 is divided between all the disks in a round-robin
> fashion, to avoid one disk becoming the bottleneck for all writes. I
> think that RAID 4 is where one disk holds all the parity.
> [http://en.wikipedia.org/wiki/RAID5#RAID_5]

You're right, and I did start to write that in my original email but  
realised I was late for work and thought I probably shouldn't be going  
too much into the implementation details of RAID5, so I just "lied",  
tut tut!

Martin.

From boxbackup-dev@fluffy.co.uk  Fri Apr 21 11:03:46 2006
From: boxbackup-dev@fluffy.co.uk (Chris Wilson)
Date: Fri, 21 Apr 2006 10:03:46 +0000
Subject: [Box Backup-dev] [Doc] A few more things to look at...
In-Reply-To: <4440AFB4.8090007@reedtz.com>
References: <4440AFB4.8090007@reedtz.com>
Message-ID: <1145613826.26289.2.camel@localhost>

Hi Per,

Great work! Just one question though, for everyone. The bbstoreaccounts
page says:

> Longer numbers infer more directories in the structure, so as an
> example 3952697264 as the last object ID gives 0xEB995FB0, which
> translates to a backup pathname of 0e/b9/95/f0/b0.rfw.

As I understand the translation algorithm, the actual path should be
"eb/99/5f/ob0.rfw". Is that correct?

Cheers, Chris.
-- 
  ___ __     _
 / __/ / ,__(_)_  | Chris Wilson <0000 at qwirx.com> - Cambs UK |
/ (_/ ,\/ _/ /_ \ | Security/C/C++/Java/Perl/SQL/HTML Developer |
\ _/_/_/_//_/___/ | We are GNU-free your mind-and your software |


From boxbackup-dev@fluffy.co.uk  Fri Apr 21 11:03:46 2006
From: boxbackup-dev@fluffy.co.uk (Chris Wilson)
Date: Fri, 21 Apr 2006 10:03:46 +0000
Subject: [Box Backup-dev] [Doc] A few more things to look at...
In-Reply-To: <4440AFB4.8090007@reedtz.com>
References: <4440AFB4.8090007@reedtz.com>
Message-ID: <1145613826.26289.2.camel@localhost>

Hi Per,

Great work! Just one question though, for everyone. The bbstoreaccounts
page says:

> Longer numbers infer more directories in the structure, so as an
> example 3952697264 as the last object ID gives 0xEB995FB0, which
> translates to a backup pathname of 0e/b9/95/f0/b0.rfw.

As I understand the translation algorithm, the actual path should be
"eb/99/5f/ob0.rfw". Is that correct?

Cheers, Chris.
-- 
  ___ __     _
 / __/ / ,__(_)_  | Chris Wilson <0000 at qwirx.com> - Cambs UK |
/ (_/ ,\/ _/ /_ \ | Security/C/C++/Java/Perl/SQL/HTML Developer |
\ _/_/_/_//_/___/ | We are GNU-free your mind-and your software |


From boxbackup-dev@fluffy.co.uk  Fri Apr 21 11:06:26 2006
From: boxbackup-dev@fluffy.co.uk (Chris Wilson)
Date: Fri, 21 Apr 2006 10:06:26 +0000
Subject: [Box Backup-dev] [Doc] A few more things to look at...
In-Reply-To: <4440AFB4.8090007@reedtz.com>
References: <4440AFB4.8090007@reedtz.com>
Message-ID: <1145613986.26289.5.camel@localhost>

Hi Per,

Also in bbstoreaccounts: the client store marker is used by the client
to ensure that nobody has modified the store between backup runs,
allowing it to use its cached information about the files and
directories already on the store. The client store marker starts at
zero, and is incremented by the client every time it successfully
completes a backup. At the start of the run, the marker is compared to
the expected value, and if different, the cached data is discarded and
each directory on the store is rescanned.

Cheers, Chris.
-- 
  ___ __     _
 / __/ / ,__(_)_  | Chris Wilson <0000 at qwirx.com> - Cambs UK |
/ (_/ ,\/ _/ /_ \ | Security/C/C++/Java/Perl/SQL/HTML Developer |
\ _/_/_/_//_/___/ | We are GNU-free your mind-and your software |


From boxbackup-dev@fluffy.co.uk  Sat Apr 22 08:56:19 2006
From: boxbackup-dev@fluffy.co.uk (Ben Summers)
Date: Sat, 22 Apr 2006 08:56:19 +0100
Subject: [Box Backup-dev] COMMIT r553
Message-ID: <92311E00-4FB2-4EA4-9286-E12DBB866015@fluffy.co.uk>

Martin Ebourne wrote:
>
> Trac is one of the better systems around at the moment, and integrates
> particularly well with svn. Ben did mention he was thinking of
> installing it some time ago, but he's not said anything recently.

I am still intending to install Trac, hopefully within a couple of  
weeks. Needs to be done really, and there are more issues with other  
options. Assuming that Trac installation isn't too difficult.

Ben






From boxbackup-dev@fluffy.co.uk  Mon Apr 24 12:50:42 2006
From: boxbackup-dev@fluffy.co.uk (Stefan Norlin)
Date: Mon, 24 Apr 2006 13:50:42 +0200
Subject: [Box Backup-dev] Problem/unportability with malloc(0) on AIX
Message-ID: <029201c66795$510c5ab0$1601060a@cs>

Hi,

in my porting efforts on AIX I have comes across that
sometime malloc is called with a size argument of 0.

On Linux a pointer is returned anyway while on AIX
NULL is returned (with errno set to EINVAL) and an
exception is thrown.

I am unsure whether the malloc(0) call is correct first
place but the behavor is anyway different on different
OS:s.

Any comments on this and any ideas how to handle it?

There is a long discussion regarding this here:

http://groups.google.com/group/comp.unix.aix/browse_frm/thread/96cb665447260f64/7f8e35f319021cfd?tvc=1#7f8e35f319021cfd

With some hotfix using "mallopt(1, 0)".

Regards,
Stefan


From boxbackup-dev@fluffy.co.uk  Mon Apr 24 15:06:48 2006
From: boxbackup-dev@fluffy.co.uk (Martin Ebourne)
Date: Mon, 24 Apr 2006 15:06:48 +0100
Subject: [Box Backup-dev] Problem/unportability with malloc(0) on AIX
In-Reply-To: <029201c66795$510c5ab0$1601060a@cs>
References: <029201c66795$510c5ab0$1601060a@cs>
Message-ID: <20060424150648.oaq4j6liv44o0cks@ebourne.me.uk>

Stefan Norlin <stefan.norlin@infoflexconnect.se> wrote:
> in my porting efforts on AIX I have comes across that
> sometime malloc is called with a size argument of 0.
>
> On Linux a pointer is returned anyway while on AIX
> NULL is returned (with errno set to EINVAL) and an
> exception is thrown.
>
> I am unsure whether the malloc(0) call is correct first
> place but the behavor is anyway different on different
> OS:s.

As much as I don't like AIX, it is entirely right here. As far as I  
know C++ agrees with C on this matter, and the ISO C standard says  
that an implementation shall either return a NULL pointer or a unique  
pointer (which may not be dereferenced) in the case of malloc(0).

It also says that realloc(NULL, size) will work, and that free(NULL)  
is safe, so the code can handle nulls ok if it wants to.

This is a bug in box, so if you can track down where it is being  
allocated we can look at fixing it.

Cheers,

Martin.

From boxbackup-dev@fluffy.co.uk  Mon Apr 24 15:23:21 2006
From: boxbackup-dev@fluffy.co.uk (Stefan Norlin)
Date: Mon, 24 Apr 2006 16:23:21 +0200
Subject: [Box Backup-dev] Problem/unportability with malloc(0) on AIX
References: <029201c66795$510c5ab0$1601060a@cs> <20060424150648.oaq4j6liv44o0cks@ebourne.me.uk>
Message-ID: <03e801c667aa$a3d64e30$1601060a@cs>

> This is a bug in box, so if you can track down where it is being 
> allocated we can look at fixing it.

Hi Martin,

it is the malloc in the section:

 // Allocate a new block (this way to be exception safe)
        char *pblock = (char*)malloc(size);
        if(pblock == 0)
        {
                throw std::bad_alloc();
        }

in lib/common/StreamableMemBlock.cpp

Function: void StreamableMemBlock::ReadFromStream(IOStream &rStream, int 
Timeout)

Regards,
Stefan


From boxbackup-dev@fluffy.co.uk  Mon Apr 24 16:46:12 2006
From: boxbackup-dev@fluffy.co.uk (Martin Ebourne)
Date: Mon, 24 Apr 2006 16:46:12 +0100
Subject: [Box Backup-dev] Problem/unportability with malloc(0) on AIX
In-Reply-To: <03e801c667aa$a3d64e30$1601060a@cs>
References: <029201c66795$510c5ab0$1601060a@cs>
 <20060424150648.oaq4j6liv44o0cks@ebourne.me.uk>
 <03e801c667aa$a3d64e30$1601060a@cs>
Message-ID: <20060424164612.j39ufkhhb4k8c8cs@ebourne.me.uk>

Stefan Norlin <stefan.norlin@infoflexconnect.se> wrote:
> Function: void StreamableMemBlock::ReadFromStream(IOStream &rStream,
> int Timeout)

Clues such as where it is called from in this case and why it is 0 if  
you uncovered any would all be helpful.

Cheers,

Martin.

From boxbackup-dev@fluffy.co.uk  Mon Apr 24 18:02:52 2006
From: boxbackup-dev@fluffy.co.uk (Stefan Norlin)
Date: Mon, 24 Apr 2006 19:02:52 +0200
Subject: [Box Backup-dev] Problem/unportability with malloc(0) on AIX
References: <029201c66795$510c5ab0$1601060a@cs><20060424150648.oaq4j6liv44o0cks@ebourne.me.uk><03e801c667aa$a3d64e30$1601060a@cs> <20060424164612.j39ufkhhb4k8c8cs@ebourne.me.uk>
Message-ID: <003801c667c0$ec7f3820$0101050a@stenorhem>

> Clues such as where it is called from in this case and why it is 0 if  
> you uncovered any would all be helpful.

Of course, should have been a bit more specific from the start.

I run bbackupquery towards a newly created account and use the "ls"
command to list files (which there aren't any since the account is new).

So, I guess it occurs when there are no directory entries to be read
from the stream.

The call is from BackupQueries.cpp in this section:

        // Retrieve the directory from the stream following
        BackupStoreDirectory dir;
        std::auto_ptr<IOStream> dirstream(mrConnection.ReceiveStream());

        // THIS CALL CAUSES THE EXCEPTION, Stefan
        dir.ReadFromStream(*dirstream, mrConnection.GetTimeout());

        // Then... display everything
        BackupStoreDirectory::Iterator i(dir);

Stefan

From boxbackup-dev@fluffy.co.uk  Tue Apr 25 14:49:22 2006
From: boxbackup-dev@fluffy.co.uk (Stefan Norlin)
Date: Tue, 25 Apr 2006 15:49:22 +0200
Subject: [Box Backup-dev] AIX 5 patch
Message-ID: <030201c6686f$0f277320$1601060a@cs>

This is a multi-part message in MIME format.

------=_NextPart_000_02FE_01C6687F.D28C6770
Content-Type: multipart/alternative;
	boundary="----=_NextPart_001_02FF_01C6687F.D28C6770"


------=_NextPart_001_02FF_01C6687F.D28C6770
Content-Type: text/plain;
	charset="iso-8859-15"
Content-Transfer-Encoding: quoted-printable

Hi,

with the attached diff I can compile on AIX 5 and Box Backup
works seemingly ok. I do not consider it a clean portability work
but it is an indication where something needs to be done. Also
there are very few and minor changes which I think is good.

All tests do not pass, I am looking at that. raidfile is one problem
and a bbstored that does not stop is another.

However, I am able to take snapshot backup, browse it and compare
it ok using bbackupquery.

The workaround for malloc(0) is not beatiful but it solves my
problem temporarily.

The installed version of BDB 4.4 depends on pthread library from
which the "hack" in configure.ac originates.

It would be great to be able to link OpenSSL and libdb statically in
order to not have to compile Box for each installation when the OS
versions are not exactly the same and therefore dependencies do
not always work out with dynamic libraries.

For what it is worth...

Regards,
Stefan

------=_NextPart_001_02FF_01C6687F.D28C6770
Content-Type: text/html;
	charset="iso-8859-15"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-15">
<META content=3D"MSHTML 6.00.2900.2802" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Hi,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>with the attached diff I can compile on =
AIX 5 and=20
Box Backup</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>works seemingly ok. I do not consider =
it=20
</FONT><FONT face=3DArial size=3D2>a clean portability work</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>but it is an indication where something =

</FONT><FONT face=3DArial size=3D2>needs to be done. Also</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>there are very few and minor changes =
</FONT><FONT=20
face=3DArial size=3D2>which I think is good.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>All tests do not pass, I am looking at =
that.=20
raidfile is one problem</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>and a bbstored that does not stop is=20
another.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>However, I am able to take snapshot =
backup, browse=20
it and compare</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>it </FONT><FONT face=3DArial =
size=3D2>ok using=20
bbackupquery.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>The workaround for malloc(0) is not =
beatiful but it=20
solves my</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>problem temporarily.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>The installed version of BDB 4.4 =
depends on pthread=20
library from</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>which the "hack" in configure.ac=20
originates.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>It would be great to be able to link =
OpenSSL and=20
libdb statically in</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>order to </FONT><FONT face=3DArial =
size=3D2>not have to=20
compile Box for each installation when the OS</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>versions are not exactly the same and =
therefore=20
dependencies do</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>not always work out with dynamic=20
libraries.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>For what it is worth...</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Regards,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Stefan</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV></BODY></HTML>

------=_NextPart_001_02FF_01C6687F.D28C6770--

------=_NextPart_000_02FE_01C6687F.D28C6770
Content-Type: text/plain;
	name="aix5-svn-diff.txt"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
	filename="aix5-svn-diff.txt"

Index: infrastructure/BoxPlatform.pm.in=0A=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=0A=
--- infrastructure/BoxPlatform.pm.in    (revision 555)=0A=
+++ infrastructure/BoxPlatform.pm.in    (working copy)=0A=
@@ -17,7 +17,7 @@=0A=
        $build_os =3D 'CYGWIN' if $build_os =3D~ m/CYGWIN/;=0A=
 =0A=
        $make_command =3D ($build_os eq 'Darwin') ? 'bsdmake' : =
($build_os eq=0A=
'SunOS') ? 'gmake' : 'make';=0A=
-       $bsd_make =3D ($build_os ne 'Linux' && $build_os ne 'CYGWIN' &&=0A=
        $build_os ne "SunOS");=0A=
+       $bsd_make =3D ($build_os ne 'AIX' && $build_os ne 'Linux' && =
$build_os=0A=
ne 'CYGWIN' && $build_os ne "SunOS");=0A=
 =0A=
        # blank extra flags by default=0A=
        $platform_compile_line_extra =3D '@CPPFLAGS@ @CXXFLAGS@=0A=
@CXXFLAGS_STRICT@';=0A=
Index: configure.ac=0A=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=0A=
--- configure.ac        (revision 555)=0A=
+++ configure.ac        (working copy)=0A=
@@ -43,6 +43,8 @@=0A=
 AC_CHECK_LIB([z], [zlibVersion],, [AC_MSG_ERROR([[cannot find zlib]])])=0A=
 VL_LIB_READLINE([have_libreadline=3Dyes], [have_libreadline=3Dno])=0A=
 =0A=
+AC_SEARCH_LIBS([pthread_cond_init], [pthread])=0A=
+=0A=
 ## Check for Berkely DB. Restrict to certain versions=0A=
 AX_PATH_BDB(, [=0A=
   LIBS=3D"$BDB_LIBS $LIBS"=0A=
Index: lib/common/BoxPlatform.h=0A=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=0A=
--- lib/common/BoxPlatform.h    (revision 555)=0A=
+++ lib/common/BoxPlatform.h    (working copy)=0A=
@@ -46,6 +46,11 @@=0A=
        #define PLATFORM_CLIB_FNS_INTERCEPTION_IMPOSSIBLE=0A=
 #endif=0A=
 =0A=
+// On AIX too...=0A=
+#ifdef _AIX=0A=
+#define PLATFORM_CLIB_FNS_INTERCEPTION_IMPOSSIBLE=0A=
+#endif=0A=
+=0A=
 // Disable memory testing under Darwin, it just doesn't like it very =
much.=0A=
 #ifdef __APPLE__=0A=
        // TODO: We really should get some decent leak detection code.=0A=
Index: lib/common/StreamableMemBlock.cpp=0A=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=0A=
--- lib/common/StreamableMemBlock.cpp   (revision 555)=0A=
+++ lib/common/StreamableMemBlock.cpp   (working copy)=0A=
@@ -260,6 +260,11 @@=0A=
        =0A=
        =0A=
        // Allocate a new block (this way to be exception safe)=0A=
+#ifdef _AIX=0A=
+       // Ugly hack to avoid returning NULL on AIX when size =3D=3D 0=0A=
+       // This should be fixed some other way...=0A=
+       if(size =3D=3D 0) size =3D 1;=0A=
+#endif=0A=
        char *pblock =3D (char*)malloc(size);=0A=
        if(pblock =3D=3D 0)=0A=
        {=0A=

------=_NextPart_000_02FE_01C6687F.D28C6770--


From boxbackup-dev@fluffy.co.uk  Wed Apr 26 07:14:16 2006
From: boxbackup-dev@fluffy.co.uk (boxbackup-dev@fluffy.co.uk)
Date: Wed, 26 Apr 2006 06:14:16 +0000 (GMT)
Subject: [Box Backup-dev] COMMIT r558 - box/trunk/documentation/boxbackup
Message-ID: <20060426061416.3F25695@s0g0.pems.testserver.co.uk>

Author: per
Date: 2006-04-26 06:14:12 +0000 (Wed, 26 Apr 2006)
New Revision: 558

Added:
   box/trunk/documentation/boxbackup/bbstored-certs.xml
   box/trunk/documentation/boxbackup/bbstored-config.xml
   box/trunk/documentation/boxbackup/raidfile-config.xml
Modified:
   box/trunk/documentation/boxbackup/Makefile
Log:
Added raidfile-config, bbstored-certs and bbstored-config.

Also, hacked makefile to do the right thing.


Modified: box/trunk/documentation/boxbackup/Makefile
===================================================================
--- box/trunk/documentation/boxbackup/Makefile	2006-04-15 08:15:33 UTC (rev 557)
+++ box/trunk/documentation/boxbackup/Makefile	2006-04-26 06:14:12 UTC (rev 558)
@@ -36,9 +36,9 @@
 man-pages/.there:
 	if [ ! -d man-pages ]; then mkdir man-pages; touch man-pages/.there; fi
 
-man-nroff: bbackupquery.1 bbackupctl.1 bbstoreaccounts.1
+man-nroff: bbackupquery.1 bbackupctl.1 bbstoreaccounts.1 bbstored-config.1 raidfile-config.1 bbstored-certs.1
 
-man-html: bbackupquery.html bbackupctl.html bbstoreaccounts.html
+man-html: bbackupquery.html bbackupctl.html bbstoreaccounts.html bbstored-config.html raidfile-config.html bbstored-certs.html
 
 %.html: %.xml
 	$(DBPROC) -o $@ $(NOCHUNKBOOKXSL) $<

Added: box/trunk/documentation/boxbackup/bbstored-certs.xml
===================================================================
--- box/trunk/documentation/boxbackup/bbstored-certs.xml	2006-04-15 08:15:33 UTC (rev 557)
+++ box/trunk/documentation/boxbackup/bbstored-certs.xml	2006-04-26 06:14:12 UTC (rev 558)
@@ -0,0 +1,125 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<refentry>
+  <refmeta>
+    <refentrytitle>bbstored-certs</refentrytitle>
+
+    <manvolnum>1</manvolnum>
+  </refmeta>
+
+  <refnamediv>
+    <refname>bbstored-certs</refname>
+
+    <refpurpose>Manage certificates for the Box Backup system</refpurpose>
+  </refnamediv>
+
+  <refsynopsisdiv>
+    <cmdsynopsis>
+      <command>bbstored-certs &lt;certs-dir&gt; &lt;command&gt;
+      [&lt;arguments&gt;]</command>
+    </cmdsynopsis>
+  </refsynopsisdiv>
+
+  <refsection>
+    <title>Description</title>
+
+    <para><literal>bbstored-certs</literal> creates and signs certificates for
+    use in Box Backup. It allows the user to create and sign the server keys,
+    as well as signing client keys.</para>
+
+    <para>All commands must be followed by the <literal>certs-dir</literal>,
+    which is the directory in which the certificates are stored.</para>
+
+    <refsection>
+      <title>Commands</title>
+
+      <para>There are 3 commands:</para>
+
+      <itemizedlist>
+        <listitem>
+          <para><literal>init</literal>: Create the
+          <literal>certs-dir</literal>, and generate the server keys for
+          bbstored. <literal>certs-dir</literal> cannot exist before running
+          the command.</para>
+        </listitem>
+
+        <listitem>
+          <para><literal>sign-server &lt;servercsrfile&gt;</literal>: Sign the
+          server certificate. The <literal>servercsrfile</literal> is the file
+          generated by the <literal>init</literal> command.</para>
+        </listitem>
+
+        <listitem>
+          <para><literal>sign &lt;clientcsrfile&gt;</literal>: Sign a client
+          certificate. The <literal>clientcsrfile</literal> is generated
+          during client setup. See <literal>bbackupd-config(1)</literal>. Send
+          the signed certificate back to the client, and install according to
+          the instructions given by <literal>bbackupd-config</literal>.</para>
+        </listitem>
+      </itemizedlist>
+    </refsection>
+  </refsection>
+
+  <refsection>
+    <title>Author</title>
+
+    <para>Ben Summers and contributors. For help, please go to the <ulink
+    url="http://boxbackup.hostworks.ca/">Wiki</ulink>, or subscribe to the Box
+    Backup <ulink
+    url="http://lists.warhead.org.uk/mailman/listinfo/boxbackup">mailing
+    list.</ulink></para>
+  </refsection>
+
+  <refsection>
+    <title>See Also</title>
+
+    <para><literal>bbstored-config(1)</literal></para>
+
+    <para><literal>bbstored.conf(5)</literal></para>
+
+    <para><literal>bbstoreaccounts(1)</literal></para>
+  </refsection>
+
+  <refsection>
+    <title>Files</title>
+
+    <para><literal>raidfile-config</literal> generates the raidfile.conf(5)
+    file.</para>
+  </refsection>
+
+  <refsection>
+    <title>Bugs</title>
+
+    <para>If you find a bug in Box Backup, and you want to let us know about
+    it, join the <ulink
+    url="http://lists.warhead.org.uk/mailman/listinfo/boxbackup">mailing
+    list</ulink>, and send a description of the problem there.</para>
+
+    <para>To report a bug, give us at least the following information:</para>
+
+    <itemizedlist>
+      <listitem>
+        <para>The version of Box Backup you are running</para>
+      </listitem>
+
+      <listitem>
+        <para>The platform you are running on (Hardware and OS), for both
+        client and server.</para>
+      </listitem>
+
+      <listitem>
+        <para>If possible attach your config files (bbstored.conf,
+        bbackupd.conf) to the bug report.</para>
+      </listitem>
+
+      <listitem>
+        <para>Also attach any log file output that helps shed light on the
+        problem you are seeing.</para>
+      </listitem>
+
+      <listitem>
+        <para>And last but certainly not least, a description of what you are
+        seeing, in as much detail as possible.</para>
+      </listitem>
+    </itemizedlist>
+  </refsection>
+</refentry>
\ No newline at end of file

Added: box/trunk/documentation/boxbackup/bbstored-config.xml
===================================================================
--- box/trunk/documentation/boxbackup/bbstored-config.xml	2006-04-15 08:15:33 UTC (rev 557)
+++ box/trunk/documentation/boxbackup/bbstored-config.xml	2006-04-26 06:14:12 UTC (rev 558)
@@ -0,0 +1,140 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<refentry>
+  <refmeta>
+    <refentrytitle>bbstored-config</refentrytitle>
+
+    <manvolnum>1</manvolnum>
+  </refmeta>
+
+  <refnamediv>
+    <refname>bbstored-config</refname>
+
+    <refpurpose>Create config files for bbstored</refpurpose>
+  </refnamediv>
+
+  <refsynopsisdiv>
+    <cmdsynopsis>
+      <command>bbstored-config &lt;configdir&gt; &lt;servername&gt;
+      &lt;username&gt;</command>
+    </cmdsynopsis>
+  </refsynopsisdiv>
+
+  <refsection>
+    <title>Description</title>
+
+    <para>The <literal>bbstored-config</literal> script creates config files
+    and server certificates for a bbstored instance. It takes three
+    parameters:</para>
+
+    <itemizedlist>
+      <listitem>
+        <para><literal>configdir</literal>: The directory where config files
+        will reside. A subdirectory bbstored will be created, where several
+        config files will reside. the <literal>bbstored.conf</literal> file
+        will be created in <literal>configdir</literal>.</para>
+      </listitem>
+
+      <listitem>
+        <para><literal>servername</literal>: The name of the server that is
+        being configured. Usually the fully qualified domain name of the
+        machine in question.</para>
+      </listitem>
+
+      <listitem>
+        <para><literal>username</literal>: The name of the user that should be
+        running the bbstored processes. Recommended name:
+        _<literal>bbstored.</literal></para>
+      </listitem>
+    </itemizedlist>
+
+    <para>A valid raidfile.conf(5) must be found in configdir. Several steps
+    are taken during the run of bbstored-config:</para>
+
+    <itemizedlist>
+      <listitem>
+        <para>Configuration files are created.</para>
+      </listitem>
+
+      <listitem>
+        <para>Server certificates are created. This requires interaction from
+        the operator.</para>
+      </listitem>
+
+      <listitem>
+        <para>The raid volumes are checked, to ensure that the configuration
+        is consistent, and will work.</para>
+      </listitem>
+
+      <listitem>
+        <para>Instructions for next steps to take are shown. These steps may
+        be different for different OS platforms, so pay close attention to
+        these instructions.</para>
+      </listitem>
+    </itemizedlist>
+  </refsection>
+
+  <refsection>
+    <title>Author</title>
+
+    <para>Ben Summers and contributors. For help, please go to the <ulink
+    url="http://boxbackup.hostworks.ca/">Wiki</ulink>, or subscribe to the Box
+    Backup <ulink
+    url="http://lists.warhead.org.uk/mailman/listinfo/boxbackup">mailing
+    list.</ulink></para>
+  </refsection>
+
+  <refsection>
+    <title>See Also</title>
+
+    <para><literal>raidfile-config(1)</literal></para>
+
+    <para><literal>bbstored.conf(5)</literal></para>
+
+    <para><literal>raidfile.conf(5)</literal></para>
+  </refsection>
+
+  <refsection>
+    <title>Files</title>
+
+    <para><literal>bbstoreaccounts</literal> uses the Box Backup server
+    configuration file, usually located in
+    <filename>/etc/box/bbstored.conf</filename>.</para>
+  </refsection>
+
+  <refsection>
+    <title>Bugs</title>
+
+    <para>If you find a bug in Box Backup, and you want to let us know about
+    it, join the <ulink
+    url="http://lists.warhead.org.uk/mailman/listinfo/boxbackup">mailing
+    list</ulink>, and send a description of the problem there.</para>
+
+    <para>To report a bug, give us at least the following information:</para>
+
+    <itemizedlist>
+      <listitem>
+        <para>The version of Box Backup you are running</para>
+      </listitem>
+
+      <listitem>
+        <para>The platform you are running on (Hardware and OS), for both
+        client and server.</para>
+      </listitem>
+
+      <listitem>
+        <para>If possible attach your config files (bbstored.conf,
+        bbackupd.conf) to the bug report.</para>
+      </listitem>
+
+      <listitem>
+        <para>Also attach any log file output that helps shed light on the
+        problem you are seeing.</para>
+      </listitem>
+
+      <listitem>
+        <para>And last but certainly not least, a description of what you are
+        seeing, in as much detail as possible.</para>
+      </listitem>
+    </itemizedlist>
+  </refsection>
+</refentry>
\ No newline at end of file

Added: box/trunk/documentation/boxbackup/raidfile-config.xml
===================================================================
--- box/trunk/documentation/boxbackup/raidfile-config.xml	2006-04-15 08:15:33 UTC (rev 557)
+++ box/trunk/documentation/boxbackup/raidfile-config.xml	2006-04-26 06:14:12 UTC (rev 558)
@@ -0,0 +1,143 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<refentry>
+  <refmeta>
+    <refentrytitle>raidfile-config</refentrytitle>
+
+    <manvolnum>1</manvolnum>
+  </refmeta>
+
+  <refnamediv>
+    <refname>raidfile-config</refname>
+
+    <refpurpose>Configure Box Backup's RAID files</refpurpose>
+  </refnamediv>
+
+  <refsynopsisdiv>
+    <cmdsynopsis>
+      <command>raidfile-config &lt;configdir&gt; &lt;blocksize&gt;
+      &lt;dir1&gt; [&lt;dir2&gt; &lt;dir3&gt;]</command>
+    </cmdsynopsis>
+  </refsynopsisdiv>
+
+  <refsection>
+    <title>Description</title>
+
+    <para>raidfile-config creates a raidfile.conf file for Box Backup. This
+    file holds information about the directories used to store backups in. Box
+    Backup supports userland RAID, in a restricted RAID5 configuration, where
+    3 and only 3 'drives' are supported. You can read more about RAID5 (and
+    other RAID-levels) <ulink
+    url="http://en.wikipedia.org/wiki/Redundant_array_of_independent_disks#RAID_5">here</ulink>.
+    </para>
+
+    <refsection>
+      <title>Parameters</title>
+
+      <para>The parameters are as follows:</para>
+
+      <itemizedlist>
+        <listitem>
+          <para><literal>configdir</literal>: The directory path where
+          configuration files are located. Usually this is
+          <literal>/etc/box</literal>. <literal>raidfile.conf</literal> will
+          be written in this directory.</para>
+        </listitem>
+
+        <listitem>
+          <para><literal>blocksize</literal>: The block size used for file
+          storage in the system, in bytes. Using a multple of the file system
+          block size is a good strategy. Depending on the size of the files
+          you will be backing up, this multiple varies. Of course it also
+          depends on the native block size of your file system.</para>
+        </listitem>
+
+        <listitem>
+          <para><literal>dir1</literal>: The first directory in the built-in
+          RAID array.</para>
+        </listitem>
+
+        <listitem>
+          <para><literal>dir2</literal>: The second directory in the built-in
+          RAID array. If you are not using the built-in RAID functionality,
+          this field should be ignored. You should not use the built-in RAID,
+          when you have a hardware RAID solution, or if you're using another
+          type of software RAID (like md on Linux).</para>
+        </listitem>
+
+        <listitem>
+          <para><literal>dir3</literal>: The third directory in the built-in
+          RAID array. The same notes that apply to <literal>dir2</literal>
+          also apply to <literal>dir3</literal>.</para>
+        </listitem>
+      </itemizedlist>
+
+      <para>Note that there are currently no way to add multiple disk sets to
+      the raidfile.conf file using command line tools, etc. See
+      raidfile.conf(5) for details on adding more disks</para>
+    </refsection>
+  </refsection>
+
+  <refsection>
+    <title>Author</title>
+
+    <para>Ben Summers and contributors. For help, please go to the <ulink
+    url="http://boxbackup.hostworks.ca/">Wiki</ulink>, or subscribe to the Box
+    Backup <ulink
+    url="http://lists.warhead.org.uk/mailman/listinfo/boxbackup">mailing
+    list.</ulink></para>
+  </refsection>
+
+  <refsection>
+    <title>See Also</title>
+
+    <para><literal>bbstored-config(1)</literal></para>
+
+    <para><literal>bbstored.conf(5)</literal></para>
+
+    <para><literal>raidfile.conf(5)</literal></para>
+  </refsection>
+
+  <refsection>
+    <title>Files</title>
+
+    <para><literal>raidfile-config</literal> generates the raidfile.conf(5)
+    file.</para>
+  </refsection>
+
+  <refsection>
+    <title>Bugs</title>
+
+    <para>If you find a bug in Box Backup, and you want to let us know about
+    it, join the <ulink
+    url="http://lists.warhead.org.uk/mailman/listinfo/boxbackup">mailing
+    list</ulink>, and send a description of the problem there.</para>
+
+    <para>To report a bug, give us at least the following information:</para>
+
+    <itemizedlist>
+      <listitem>
+        <para>The version of Box Backup you are running</para>
+      </listitem>
+
+      <listitem>
+        <para>The platform you are running on (Hardware and OS), for both
+        client and server.</para>
+      </listitem>
+
+      <listitem>
+        <para>If possible attach your config files (bbstored.conf,
+        bbackupd.conf) to the bug report.</para>
+      </listitem>
+
+      <listitem>
+        <para>Also attach any log file output that helps shed light on the
+        problem you are seeing.</para>
+      </listitem>
+
+      <listitem>
+        <para>And last but certainly not least, a description of what you are
+        seeing, in as much detail as possible.</para>
+      </listitem>
+    </itemizedlist>
+  </refsection>
+</refentry>
\ No newline at end of file


From boxbackup-dev@fluffy.co.uk  Wed Apr 26 22:36:09 2006
From: boxbackup-dev@fluffy.co.uk (boxbackup-dev@fluffy.co.uk)
Date: Wed, 26 Apr 2006 21:36:09 +0000 (GMT)
Subject: [Box Backup-dev] COMMIT r559 - box/trunk/documentation/boxbackup
Message-ID: <20060426213609.6384795@s0g0.pems.testserver.co.uk>

Author: per
Date: 2006-04-26 21:36:06 +0000 (Wed, 26 Apr 2006)
New Revision: 559

Modified:
   box/trunk/documentation/boxbackup/bbstoreaccounts.xml
Log:
Minor edit in bbstoreaccounts.xml


Modified: box/trunk/documentation/boxbackup/bbstoreaccounts.xml
===================================================================
--- box/trunk/documentation/boxbackup/bbstoreaccounts.xml	2006-04-26 06:14:12 UTC (rev 558)
+++ box/trunk/documentation/boxbackup/bbstoreaccounts.xml	2006-04-26 21:36:06 UTC (rev 559)
@@ -112,7 +112,7 @@
 
           <para>Display information about the given account. Example:</para>
 
-          <programlisting> root]# bbstoreaccounts info 1
+          <programlisting>[root]# bbstoreaccounts info 1
                   Account ID: 00000001
               Last object ID: 58757
                  Blocks used: 9864063 (38531.50Mb)
@@ -141,7 +141,7 @@
               numbers infer more directories in the structure, so as an
               example 3952697264 as the last object ID gives 0xEB995FB0, which
               translates to a backup pathname of
-              <literal>0e/b9/95/f0/b0.rfw.</literal></para>
+              <literal>eb/99/5f/ob0.rfw.</literal></para>
             </listitem>
 
             <listitem>
@@ -160,8 +160,8 @@
 
             <listitem>
               <para>Blocks used by deleted files: The number of blocks used by
-              files that have been deleted on the client. This data is at risk
-              for being removed during housekeeping.</para>
+              files that have been deleted on the client. Thi s data is at
+              risk for being removed during housekeeping.</para>
             </listitem>
 
             <listitem>


