[46112] trunk/dports/sysutils/boxbackup
ecronin at macports.org
ecronin at macports.org
Thu Jan 29 12:13:19 PST 2009
Revision: 46112
http://trac.macports.org/changeset/46112
Author: ecronin at macports.org
Date: 2009-01-29 12:13:19 -0800 (Thu, 29 Jan 2009)
Log Message:
-----------
sysutils/boxbackup
0.11rc2 has been out almost a full year now, its stable but the build
isn't polished yet. Current port is broken (uses 'cd') and I've been
running this version for a year now, so committing even though its a
devel version...
Modified Paths:
--------------
trunk/dports/sysutils/boxbackup/Portfile
Removed Paths:
-------------
trunk/dports/sysutils/boxbackup/files/accounts.html
trunk/dports/sysutils/boxbackup/files/bbackupctl.html
trunk/dports/sysutils/boxbackup/files/boxbackup.sh.in
trunk/dports/sysutils/boxbackup/files/client.html
trunk/dports/sysutils/boxbackup/files/license.html
trunk/dports/sysutils/boxbackup/files/nonroot.html
trunk/dports/sysutils/boxbackup/files/patch-BoxPlatform.pm.in.diff
trunk/dports/sysutils/boxbackup/files/restore.html
trunk/dports/sysutils/boxbackup/files/retrieve.html
trunk/dports/sysutils/boxbackup/files/server.html
trunk/dports/sysutils/boxbackup/files/serverfix.html
trunk/dports/sysutils/boxbackup/files/space.html
trunk/dports/sysutils/boxbackup/files/trouble.html
Modified: trunk/dports/sysutils/boxbackup/Portfile
===================================================================
--- trunk/dports/sysutils/boxbackup/Portfile 2009-01-29 19:52:24 UTC (rev 46111)
+++ trunk/dports/sysutils/boxbackup/Portfile 2009-01-29 20:13:19 UTC (rev 46112)
@@ -3,10 +3,10 @@
PortSystem 1.0
name boxbackup
-version 0.10
+version 0.11rc2
categories sysutils net
-maintainers ecronin at gizmolabs.org
-description completely automatic on-line backup system for UNIX.
+maintainers ecronin
+description completely automatic on-line backup system.
long_description The backup daemon, bbackupd, runs on all machines to \
be backed up. The store server daemon, bbstored runs \
on a central server. Data is sent to the store \
@@ -17,82 +17,57 @@
and cheap to use. Once set up, there should be no \
need for user or administrative intervention, apart \
from usual system maintenance.
-homepage http://www.fluffy.co.uk/boxbackup/
+homepage http://www.boxbackup.org/
platforms darwin
-master_sites sourceforge
+master_sites ${homepage}svn/box/packages/
extract.suffix .tgz
-checksums md5 2dc02d87932fdb222ed019443ddcf444
-patchfiles patch-BoxPlatform.pm.in.diff
+checksums md5 68052f963a944c717a50bd65a54375ff \
+ sha1 9ba640b1c1f2531214a54273396f8cf932d17782 \
+ rmd160 5118667aa083898c193b098fe4c876abc6cd4e7c
-depends_lib path:bin/perl:perl5 \
- port:zlib \
- port:openssl
+depends_lib path:bin/perl:perl5 port:openssl port:readline port:openssl
+##### TEMPORARY FIX; REMOVE FOR >= 0.11rc3
post-patch {
- reinplace "s|ac_default_prefix=/usr/local|ac_default_prefix=${prefix}|g" ${worksrcpath}/configure
- reinplace "s|@bindir_expanded@|${prefix}/bin|g" ${worksrcpath}/infrastructure/BoxPlatform.pm.in
- reinplace "s|__PREFIX__|${prefix}|g" ${worksrcpath}/infrastructure/BoxPlatform.pm.in
- reinplace "s|\$install_into_dir|${destroot}\$install_into_dir|g" ${worksrcpath}/infrastructure/makeparcels.pl
-
- cd ${worksrcpath}
- foreach file [exec find . -type f ( -name *.pl -o -name *-config -o -name *-certs -o -name *.cpp )] {
- reinplace "s|/usr/bin/perl|${prefix}/bin/perl|g" ${file}
- }
- foreach file { \
- bin/bbstored/BackupConstants.h \
- bin/bbackupd/bbackupd-config \
- bin/bbstored/bbstored-certs \
- bin/bbstored/bbstored-config \
- lib/common/BoxPortsAndFiles.h \
- lib/raidfile/RaidFileController.h \
- lib/raidfile/raidfile-config \
- } {
- reinplace "s|/usr/local|${prefix}|g" ${file}
- reinplace "s|/var/run|${prefix}/var/run|g" ${file}
- reinplace "s|/var/bbackupd|${prefix}/var/bbackupd|g" ${file}
- reinplace "s|/etc/box|${prefix}/etc/box|g" ${file}
- }
+ reinplace "s|sysconfdir='/etc'||g" ${worksrcpath}/configure
+ reinplace "s|localstatedir='/var/run'||g" ${worksrcpath}/configure
}
-configure.env PREFIX='${prefix}'
-configure.pre_args
+configure.args --sysconfdir=${prefix}/etc \
+ --localstatedir=${prefix}/var/bbackupd \
+ --enable-gnu-readline
destroot.target install-backup-client
-destroot.keepdirs ${destroot}${prefix}/etc/box \
- ${destroot}${prefix}/etc/box/bbackupd \
- ${destroot}${prefix}/var/run \
+destroot.keepdirs ${destroot}${prefix}/etc/box/bbackupd \
${destroot}${prefix}/var/bbackupd
-post-build {
-# Since this app does not support DESTDIR ....
- reinplace "s|/usr/local|${destroot}${prefix}|g" ${worksrcpath}/parcels/scripts/install-backup-client
- reinplace "s|/usr/local|${destroot}${prefix}|g" ${worksrcpath}/parcels/scripts/install-backup-server
-}
post-destroot {
xinstall -d -m 0700 ${destroot}${prefix}/etc/box/bbackupd
- xinstall -d -m 0700 ${destroot}${prefix}/var/bbackupd
+ xinstall -d -m 0755 ${destroot}${prefix}/var/bbackupd
- xinstall -d -m 0755 ${destroot}${prefix}/share/doc/${name}
- foreach docname {accounts bbackupctl client license nonroot restore retrieve server serverfix space trouble} {
- xinstall -m 0644 ${filespath}/${docname}.html \
- ${destroot}${prefix}/share/doc/${name}/${docname}.html
- reinplace "s|/usr/local|${prefix}|g" \
- ${destroot}${prefix}/share/doc/${name}/${docname}.html
- reinplace "s|/var/run|${prefix}/var/run|g" \
- ${destroot}${prefix}/share/doc/${name}/${docname}.html
- reinplace "s|/var/bbackupd|${prefix}/var/bbackupd|g" \
- ${destroot}${prefix}/share/doc/${name}/${docname}.html
- reinplace "s|/etc/box|${prefix}/etc/box|g" \
- ${destroot}${prefix}/share/doc/${name}/${docname}.html
- }
+ # Install the documentation
+### Broken in 0.11rc2
+# xinstall -d -m 0755 ${destroot}${prefix}/share/doc/${name}
+# foreach docname {accounts bbackupctl client license nonroot restore retrieve server serverfix space trouble} {
+# xinstall -m 0644 ${filespath}/${docname}.html \
+# ${destroot}${prefix}/share/doc/${name}/${docname}.html
+# reinplace "s|/usr/local|${prefix}|g" \
+# ${destroot}${prefix}/share/doc/${name}/${docname}.html
+# reinplace "s|/var/run|${prefix}/var/run|g" \
+# ${destroot}${prefix}/share/doc/${name}/${docname}.html
+# reinplace "s|/var/bbackupd|${prefix}/var/bbackupd|g" \
+# ${destroot}${prefix}/share/doc/${name}/${docname}.html
+# reinplace "s|/etc/box|${prefix}/etc/box|g" \
+# ${destroot}${prefix}/share/doc/${name}/${docname}.html
+# }
+}
- # Create startup rc script (if non-Darwin)
- if {![variant_isset darwin]} {
- xinstall -d -m 0755 ${destroot}${prefix}/etc/rc.d
- xinstall -m 0755 ${filespath}/boxbackup.sh.in \
- ${destroot}${prefix}/etc/rc.d/boxbackup.sh
- reinplace "s|__PREFIX__|${prefix}|g" ${destroot}${prefix}/etc/rc.d/boxbackup.sh
- }
+variant bdb \
+ description {Use Berkeley Data Base to cache bbackupd state} {
+ depends_lib-append port:db44
+
+ configure.args-append --with-bdb-headers=${prefix}/include/db44 \
+ --with-bdb-lib=${prefix}/lib/db44
}
variant server \
@@ -105,7 +80,7 @@
destroot.target-append install-backup-server
destroot.keepdirs-append ${destroot}${prefix}/etc/box/bbstored
post-destroot {
- xinstall -o bbstored -g bbstored -d -m 0700 ${destroot}${prefix}/etc/box/bbstored
+ xinstall -o bbstored -g bbstored -d -m 0770 ${destroot}${prefix}/etc/box/bbstored
}
pre-install {
@@ -121,23 +96,28 @@
ui_warn "${prefix}/etc/box/raidfile.conf is missing!"
ui_msg "You need to run 'raidfile-config' to create it."
ui_msg "See the documentation on server setup for details:"
- ui_msg " file://${prefix}/share/doc/boxbackup/server.html"
+ #ui_msg " file://${prefix}/share/doc/boxbackup/server.html"
+ ui_msg " http://www.boxbackup.org/server.html"
}
if {![file exists ${prefix}/etc/box/bbstored.conf]} {
ui_warn "${prefix}/etc/box/bbstored.conf is missing!"
ui_msg "You need to run 'bbstored-config' to create it."
ui_msg "See the documentation on server setup for details:"
- ui_msg " file://${prefix}/share/doc/boxbackup/server.html"
+ #ui_msg " file://${prefix}/share/doc/boxbackup/server.html"
+ ui_msg " http://www.boxbackup.org/server.html"
}
}
if {![file exists ${prefix}/etc/box/bbackupd.conf]} {
ui_warn "${prefix}/etc/box/bbackupd.conf is missing!"
ui_msg "You need to run 'bbackupd-config' to create it."
ui_msg "See the documentation on client setup for details:"
- ui_msg " file://${prefix}/share/doc/boxbackup/client.html"
+ #ui_msg " file://${prefix}/share/doc/boxbackup/client.html"
+ ui_msg " http://www.boxbackup.org/client.html"
}
}
+test.run yes
+
platform darwin {
startupitem.create yes
startupitem.name BoxBackup
Deleted: trunk/dports/sysutils/boxbackup/files/accounts.html
===================================================================
--- trunk/dports/sysutils/boxbackup/files/accounts.html 2009-01-29 19:52:24 UTC (rev 46111)
+++ trunk/dports/sysutils/boxbackup/files/accounts.html 2009-01-29 20:13:19 UTC (rev 46112)
@@ -1,179 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml">
-<head>
-<meta http-equiv="content-type" content="text/html;charset=iso-8859-1" />
-<title>Box Backup certificates and accounts</title>
-<link rel="stylesheet" href="bbstyles.css" type="text/css" />
-</head>
-<body>
-<div align="center">
-<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>
-<div id="page">
-
-
-<h1>Box Backup certificates and accounts</h1>
-
-<p>There are two steps involved to create an account. You need to create the account on the
-server, and sign a certificate to give the client permission to connect to the server.</p>
-
-<p>Running a Certification Authority for TLS (SSL) connections is not trivial. However,
-I have written a script to do most of the work in a way which is good enough for most
-deployments.</p>
-
-<h2>Warning about clock times</h2>
-
-<p>SSL certificates contain validity dates, including a "valid from" time. If the clock on the
-machine which signs the certificates is not syncronised to the clocks of the machines using these
-certificates, you will probably get strange errors until the start time is reached on all
-machines.</p>
-
-<p>If you get strange errors when attempting to use new certificates, check the clocks! You will
-probably just need to wait a while until the certificates become valid, rather than having to
-regenerate them.</p>
-
-<h2>Set up CA</h2>
-
-<p>It's best to do this on a machine other than your server, probably without direct network access.
-The contents of this directory control who can access your backup store server.</p>
-
-<p>To setup the basic key structure, do</p>
-
-<pre>
-/usr/local/bin/bbstored-certs ca init
-</pre>
-
-<p>(See <a href="openssl.html">OpenSSL notes</a> if you get an OpenSSL error)</p>
-
-<p>This creates the directory 'ca' in the current directory, and initialises it with basic keys.</p>
-
-<h2>Sign a server certificate</h2>
-
-<p>When you use the <tt>bbstored-config</tt> script to set up a config file for a server, it will
-generate a certificate request (CSR) for you. Transfer it to the machine with your CA, then do</p>
-
-<pre>
-/usr/local/bin/bbstored-certs ca sign-server hostname-csr.pem
-</pre>
-
-<p>which signs the certificate for the server. Follow the instructions in the output on which files to install
-on the server. The CSR file is now no longer needed. Make sure you run this command from the directory above
-the directory 'ca'.</p>
-
-<h2>Setting up an account.</h2>
-
-<p>Choose an account number for the user. This must be unique on the server, and is presented as a 31 bit
-number in hex greater than 0, for example, 1 or 75AB23C. Then on the backup store server, create the account
-with</p>
-
-<pre>
-/usr/local/bin/bbstoreaccounts create 75AB23C 0 4096M 4505M
-</pre>
-
-<p>This looks complicated. The numbers are, in order...</p>
-<ul>
-<li>The account number allocated (hex)
-<li>The RAID disc set (0 if you use raidfile-config and don't add a new set)
-<li>Soft limit (size)
-<li>Hard limit (size)
-</ul>
-
-<p>The sizes are are specified in Mb, Gb, or blocks, depending on the suffix. <tt>1M</tt> specifies 1 Mb,
-<tt>1G</tt> specifies 1 Gb, and <tt>1B</tt> specifies 1 block, the size of which depends on how you have
-configured the raidfile system with <tt>raidfile-config</tt>.</p>
-
-<p>In this example, I have allocated 4Gb (assuming you use 2048 byte blocks as per my example) as the soft limit,
-and 4Gb + 10% as the hard limit.</p>
-
-<p><b>NOTE</b> The sizes specified here are pre-RAID. So if you are using userland RAID, you are
-actually allocating two-thirds of this amount. This means that, when you take compression into account, that
-if you allocate 2Gb on the server, it'll probably hold about 2Gb of backed up files (depending on the
-compressability of those files).</p>
-
-<p>The backup client will (voluntarily) try not to upload more data than is allowed by the soft limit.
-The store server will refuse to accept a file if it would take it over the hard limit, and when doing
-housekeeping for this account, try and delete old versions and deleted files to reduce the space taken
-to below the soft limit.</p>
-
-<p>This command will create some files on disc in the raid file directories (if you run as root, the utility will
-change to the user specified in the bbstored.conf file to write them) and update the accounts file. A server
-restart is not required.</p>
-
-<p><b>NOTE</b> If you get a message saying '<tt>Exception: RaidFile (2/8)</tt>', the directories you specified
-in the raidfile.conf are not writable by the _bbstored user -- fix it, and try again.</p>
-
-<p>Finally, tell the user their account number, and the hostname of your server. They will use this to
-set up the backup client, and send you a CSR. This has the account number embedded in it, and you should
-be sure that it has the right account number in it.</p>
-
-<p>Sign this CSR with</p>
-
-<pre>
-/usr/local/bin/bbstored-certs ca sign 75AB23C-csr.pem
-</pre>
-
-<p>Don't forget to check that the embedded account number is correct! Then send the two files back to the user,
-as instructed by the script.</p>
-
-<p>Please read the <a href="trouble.html">Troubleshooting</a> page if you have problems.</p>
-
-
-<h2>Finding disc space used, and changing limits.</h2>
-
-<p>To display the space used on the server for an account, use</p>
-
-<pre>
- /usr/local/bin/bbstoreaccounts info 75AB23C
-</pre>
-
-<p>To adjust the soft and hard limits on an account, use</p>
-
-<pre>
- /usr/local/bin/bbstoreaccounts setlimit 75AB23C new-soft-limit new-hard-limit
-</pre>
-
-<p>You do not need to restart the server if the limits are changed.</p>
-
-
-<h2>Deleting an account</h2>
-
-<p>To remove an account, deleting all the stored files on the server and removing
-the account information which allows a client to log in, use</p>
-
-<pre>
- /usr/local/bin/bbstoreaccounts delete 75AB23C
-</pre>
-
-<p>This will ask for confirmation. Append <tt>yes</tt> to the command to delete
-without confirmation.</p>
-
-
-<h2>Verifying a store account</h2>
-
-<p>To check that a store account is not corrupt, and optionally fix any errors,
-use</p>
-
-<pre>
- /usr/local/bin/bbstoreaccounts check 75AB23C
- /usr/local/bin/bbstoreaccounts check 75AB23C fix
-</pre>
-
-<p>The second command will fix errors it finds, the first will merely report them.</p>
-
-<p>Append <tt>quiet</tt> to reduce the amount of output, although errors are always reported.</p>
-
-<p>See <a href="serverfix.html">fixing problems with corruption on the server</a> for more information.</p>
-
-
-<p> </p>
-<p>© Ben Summers, 2003, 2004</p>
-<p> </p>
-</div>
-</div>
-</body>
-</html>
-
-
Deleted: trunk/dports/sysutils/boxbackup/files/bbackupctl.html
===================================================================
--- trunk/dports/sysutils/boxbackup/files/bbackupctl.html 2009-01-29 19:52:24 UTC (rev 46111)
+++ trunk/dports/sysutils/boxbackup/files/bbackupctl.html 2009-01-29 20:13:19 UTC (rev 46112)
@@ -1,79 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml">
-<head>
-<meta http-equiv="content-type" content="text/html;charset=iso-8859-1" />
-<title>Controlling a backup client</title>
-<link rel="stylesheet" href="bbstyles.css" type="text/css" />
-</head>
-<body>
-<div align="center">
-<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>
-<div id="page">
-
-<h1>Controlling a backup client</h1>
-
-<p>The <tt>bbackupctl</tt> program sends control commands to the <tt>bbackupd</tt>
-daemon. It must be run as the same user as the daemon, and there is no exception for
-root.</p>
-
-<p>The command line syntax is</p>
-
-<pre>
- /usr/local/bin/bbackupctl [-q] [-c config-file] command
-</pre>
-
-<p>The <tt>-q</tt> option reduces the amount of output the program emits, and
-<tt>-c</tt> allows an alternative configuration file to be specified.</p>
-
-<p>Valid commands are</p>
-
-<dl>
-<dt>terminate
-<dd>Stop the <tt>bbackupd</tt> daemon now (equivalent to <tt>kill</tt>)
-
-<dt>reload
-<dd>Reload the configuration file (equivalent to <tt>kill -HUP</tt>)
-
-<dt>sync
-<dd>Connect to the server and syncronise files now. (See below)
-</dl>
-
-<p>It communicates with the server via a UNIX domain socket, specified in
-<tt>bbackupd.conf</tt> with the <tt>CommandSocket</tt> directive. This does not
-need to be specified, and <tt>bbackupd</tt> will run without the command socket,
-but in this case <tt>bbackupctl</tt> will not be able to communicate with the daemon.</p>
-
-<p>Some platforms cannot check the user id of the connecting process, so this
-command socket becomes a denial of service security risk. <tt>bbackupd</tt> will
-warn you when it starts up if this is the case on your platform, and you should
-consider removing the <tt>CommandSocket</tt> directive on these platforms.</p>
-
-
-<h2>Using bbackupctl to perform snapshots</h2>
-
-<p><tt>bbackupctl</tt>'s main purpose is to implement snapshot based backups,
-emulating the behaviour of traditional backup software.</p>
-
-<p>Use <tt>bbackupd-config</tt> to write a configuration file in <tt>snapshot</tt>
-mode, and then run the following command as a cron job.</p>
-
-<pre>
- /usr/local/bin/bbackupctl -q sync
-</pre>
-
-<p>This will cause the backup daemon to upload all changed files immediately.
-<tt>bbackupctl</tt> will exit almost immediately, and will not output anything
-unless there is an error.</p>
-
-
-<p> </p>
-<p>© Ben Summers, 2003, 2004</p>
-<p> </p>
-</div>
-</div>
-</body>
-</html>
\ No newline at end of file
Deleted: trunk/dports/sysutils/boxbackup/files/boxbackup.sh.in
===================================================================
--- trunk/dports/sysutils/boxbackup/files/boxbackup.sh.in 2009-01-29 19:52:24 UTC (rev 46111)
+++ trunk/dports/sysutils/boxbackup/files/boxbackup.sh.in 2009-01-29 20:13:19 UTC (rev 46112)
@@ -1,25 +0,0 @@
-#!/bin/sh
-
-case "$1" in
-start)
- [ -f __PREFIX__/etc/box/bbstored.conf ] \
- && [ -f __PREFIX__/etc/box/raidfile.conf ] \
- && __PREFIX__/bin/bbstored
- [ -f __PREFIX__/etc/box/bbackupd.conf ] \
- && __PREFIX__/bin/bbackupd
- ;;
-stop)
- /usr/bin/killall -SIGUSR1 bbackupd
- /usr/bin/killall -SIGUSR1 bbstored
- ;;
-restart)
- $0 stop
- $0 start
- ;;
-*)
- echo "Usage: `basename $0` {start|stop|restart}" >&2
- ;;
-esac
-
-exit 0
-
Deleted: trunk/dports/sysutils/boxbackup/files/client.html
===================================================================
--- trunk/dports/sysutils/boxbackup/files/client.html 2009-01-29 19:52:24 UTC (rev 46111)
+++ trunk/dports/sysutils/boxbackup/files/client.html 2009-01-29 20:13:19 UTC (rev 46112)
@@ -1,270 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml">
-<head>
-<meta http-equiv="content-type" content="text/html;charset=iso-8859-1" />
-<title>Box Backup client configuration</title>
-<link rel="stylesheet" href="bbstyles.css" type="text/css" />
-</head>
-<body>
-<div align="center">
-<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>
-<div id="page">
-
-
-<h1>Box Backup client configuration</h1>
-
-<h2>Before you start</h2>
-
-<p>Before you can do any configuration, you need to know the hostname of the server
-you will be using, and your account number on that server.</p>
-
-<p>Later in the process, you will need to send a certificate request to the administrator
-of that server for it to be signed.</p>
-
-<p>Installation is covered in the <a href="install.html">compiling and installing</a> section.
-You only need the backup-client parcel.</p>
-
-<p><b>It is important that you read all the output of the config scripts.</b> See the end
-of this page for an example.</p>
-
-<p>The backup client has to be run as root, because it needs to read all your files to
-back them up, although it is possible to back up a single user's files by running it as that user.
-(Tip: specify a directory other than /etc/box, and then give the alternate config file
-as the first argument to bbackupd). However, it will fall over if you don't give yourself
-read access to one of your files.</p>
-
-<h2>Step 1</h2>
-
-<p>Run the <tt>bbackupd-config</tt> script to generate the configuration files
-and generate a private key and certificate request.</p>
-
-<pre>
-/usr/local/bin/bbackupd-config /etc/box lazy <b>999</b> <b>hostname</b> /var/bbackupd <b>/home</b>
-</pre>
-
-<p>(See <a href="openssl.html">OpenSSL notes</a> if you get an OpenSSL error)</p>
-
-<p>The items in bold need to be changed. In order, they are the account number, the hostname
-of the server you're using, and finally, the directories you want backed up. You can include as
-many you want here.</p>
-
-<p>However, the directories you specify <b>must not</b> contain other mounted file systems within them
-at any depth. Specify them separately, one per mount point. No checks are currently made to
-catch bad configuration of this nature!</p>
-
-<p>You may also want to consider changing the mode from <i>lazy</i> to <i>snapshot</i>, depending on
-what your system is used for.</p>
-
-<dl>
-<dt>lazy
-<dd>This mode regularly scans the files, with only a rough schedule. It uploads files as and
-when they are changed, if the latest version is more than a set age. This is good for backing up
-user's documents stored on a server, and spreads the load out over the day.
-<dt>snapshot
-<dd>This mode emulates the traditional backup behaviour of taking a snapshot of the filesystem.
-The backup daemon does absolutely nothing until it is instructed to make a backup using the
-<tt>bbackupctl</tt> utility (probably as a cron job), at which point it uploads all files which
-have been changed since the last time it uploaded.
-</dl>
-
-<p>When you run the config script, it will tell you what you need to do next. Don't forget to read
-all the output. An example is shown at the end of this page, but the instructions for your installation
-may be different.</p>
-
-<h2>Step 2</h2>
-
-<p>After you have sent your certificate request off to the server administrator and received your
-certificate and CA root back, install them where instructed by the <tt>bbackupd-config</tt> script in step 1.</p>
-
-<p>You can then run the daemon (as root) by typing <tt>/usr/local/bin/bbackupd</tt>, and of course, adding
-it to your system's startup scripts. The first time it's run it will upload everything. Interrupting
-it and restarting it will only upload files which were not uploaded before - it's very tolerant.</p>
-
-<p>If you run in snapshot mode, you will need to add a cron job to schedule backups. The config
-script will tell you the exact command to use for your system.</p>
-
-<p>Please read the <a href="trouble.html">Troubleshooting</a> page if you have problems.</p>
-
-
-<p><b>Remember</b> to make a traditional backup of the keys file, as instructed. You cannot restore
-files without it.</p>
-
-<p>It is recommended that you backup up all of <tt>/etc/box</tt> as it will make things easier if you
-need to restore files. But only the keys are absolutely essential.</p>
-
-<p>If you want to see what it's doing in more detail (probably a good idea), follow the instructions in the server setup
-to create new log files with syslog.</p>
-
-
-<h2>Adding and removing backed up locations</h2>
-
-<p>By editing the <tt>/etc/box/bbackupd.conf</tt> file, you can add and remove directories
-to back up -- see comments in this file for help. Send <tt>bbackupd</tt> a HUP signal after you modify it.</p>
-
-<p>When you remove a location, it will not be marked as deleted immediately. Instead,
-<tt>bbackupd</tt> waits about two days before doing so, just in case you change your mind.
-After this, it will be eventually removed from the store by the housekeeping process.</p>
-
-
-<h2>Run as root</h2>
-
-<p>The backup client is designed to be run as root. It is possible to
-<a href="nonroot.html">run without root</a>, but this is not recommended.</p>
-
-
-<h2>Clock synchronisation for file servers</h2>
-
-<p>If you are using the backup client to backup a filesystem served from a fileserver,
-you should ideally ensure that the fileserver clocks are synchronised with the fileserver.</p>
-
-<p><tt>bbackupd</tt> will cope perfectly well if the clocks are not synchronised. Errors up
-to about half an hour cause no problems. Larger discrepancies cause a loss of efficiency
-and the potential to back up a file during a write process.</p>
-
-<p>There is a configuration parameter <tt>MaxFileTimeInFuture</tt>, which specifies how far
-in the future a file must be for it to be uploaded as soon as it is seen. You should not need
-to adjust this (default is 2 days). Instead, get those clocks synchronised.</p>
-
-
-<h2>Excluding files and directories from the backup</h2>
-
-<p>Within the <tt>bbackupd.conf</tt> file, there is a section named
-<tt>BackupLocations</tt> which specifies which locations on disc should be backed up.
-It has subsections, each of which is in the format</p>
-
-<pre>
- <i>name</i>
- {
- Path = <i>/path/of/directory</i>
- <i>(optional exclude directives)</i>
- }
-</pre>
-
-<p><i>name</i> is derived from the Path by the config script, but should merely be
-unique.</p>
-
-<p>The exclude directives are of the form</p>
-
-<pre>
- [Exclude|AlwaysInclude][File|Dir][|sRegex] = regex or full pathname
-</pre>
-
-<p>(The regex suffix is shown as 'sRegex' to make File or Dir plural)</p>
-
-<p>For example:</p>
-
-<pre>
- ExcludeDir = /home/guest-user
- ExcludeFilesRegex = *.(mp3|MP3)\$
- AlwaysIncludeFile = /home/username/veryimportant.mp3
-</pre>
-
-<p>This excludes the directory /home/guest-user from the backup along with all mp3
-files, except one MP3 file in particular.</p>
-
-<p>In general, Exclude excludes a file or directory, unless the directory is
-explicitly mentioned in a AlwaysInclude directive.</p>
-
-<p>If a directive ends in Regex, then it is a regular expression rather than a
-explicit full pathname. See</p>
-
-<pre>
- man 7 re_format
-</pre>
-
-<p>for the regex syntax on your platform.</p>
-
-
-
-
-<h2>Example configuration output</h2>
-
-<p>This is an example of output from the bbstored-config script. <b>Important:</b>
-Follow the instructions output by your script, not the ones here -- they may be different
-for your system.</p>
-
-<pre>
-# /usr/local/bin/bbackupd-config /etc/box lazy 51 server.example.com /var/bbackupd /home /etc/samba
-
-Setup bbackupd config utility.
-
-Configuration:
- Writing configuration file: /etc/box/bbackupd.conf
- Account: 51
- Server hostname: server.example.com
- Directories to back up:
- /home
- /etc/samba
-
-Note: If other file systems are mounted inside these directories, then problems may occur
-with files on the store server being renamed incorrectly. This will cause efficiency
-problems, but not affect the integrity of the backups.
-
-WARNING: Directories not checked against mountpoints. Check mounted filesystems manually.
-
-Creating /etc/box...
-Creating /etc/box/bbackupd
-Generating private key...
- [OpenSSL output omitted]
-
-Generating keys for file backup
-Writing notify script /etc/box/bbackupd/NotifyStoreFull.sh
-Writing configuration file /etc/box/bbackupd.conf
-
-===================================================================
-
-bbackupd basic configuration complete.
-
-What you need to do now...
-
-1) Make a backup of /etc/box/bbackupd/51-FileEncKeys.raw
- This should be a secure offsite backup.
- Without it, you cannot restore backups. Everything else can
- be replaced. But this cannot.
- KEEP IT IN A SAFE PLACE, OTHERWISE YOUR BACKUPS ARE USELESS.
-
-2) Send /etc/box/bbackupd/51-csr.pem
- to the administrator of the backup server, and ask for it to
- be signed.
-
-3) The administrator will send you two files. Install them as
- /etc/box/bbackupd/51-cert.pem
- /etc/box/bbackupd/serverCA.pem
- after checking their authenticity.
-
-4) You may wish to read the configuration file
- /etc/box/bbackupd.conf
- and adjust as appropraite.
-
- There are some notes in it on excluding files you do not
- wish to be backed up.
-
-5) Review the script
- /etc/box/bbackupd/NotifyStoreFull.sh
- and check that it will email the right person when the store
- becomes full. This is important -- when the store is full, no
- more files will be backed up. You want to know about this.
-
-6) Start the backup daemon with the command
- /usr/local/bin/bbackupd
- in /etc/rc.local, or your local equivalent.
- Note that bbackupd must run as root.
-
-===================================================================
-
-Remember to make a secure, offsite backup of your backup keys,
-as described in step 1 above. If you do not, you have no backups.
-</pre>
-
-<p> </p>
-<p>© Ben Summers, 2003, 2004</p>
-<p> </p>
-</div>
-</div>
-</body>
-</html>
-
Deleted: trunk/dports/sysutils/boxbackup/files/license.html
===================================================================
--- trunk/dports/sysutils/boxbackup/files/license.html 2009-01-29 19:52:24 UTC (rev 46111)
+++ trunk/dports/sysutils/boxbackup/files/license.html 2009-01-29 20:13:19 UTC (rev 46112)
@@ -1,72 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml">
-<head>
-<meta http-equiv="content-type" content="text/html;charset=iso-8859-1" />
-<title>Box Backup license</title>
-<link rel="stylesheet" href="bbstyles.css" type="text/css" />
-</head>
-<body>
-<div align="center">
-<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>
-<div id="page">
-
-<h1>Box Backup license</h1>
-
-<p>This software is licensed to you under the following terms. If you are intending
-to exploit this software commercially, please contact me for information about the additional
-tools available.</p>
-
-<h2>License</h2>
-
-<pre>
-Copyright (c) 2003, 2004
- Ben Summers. All rights reserved.
-
-Redistribution and use in source and binary forms, with or without
-modification, are permitted provided that the following conditions
-are met:
-1. Redistributions of source code must retain the above copyright
- notice, this list of conditions and the following disclaimer.
-2. Redistributions in binary form must reproduce the above copyright
- notice, this list of conditions and the following disclaimer in the
- documentation and/or other materials provided with the distribution.
-3. All use of this software and associated advertising materials must
- display the following acknowledgement:
- This product includes software developed by Ben Summers.
-4. The names of the Authors may not be used to endorse or promote
- products derived from this software without specific prior written
- permission.
-
-[Where legally impermissible the Authors do not disclaim liability for
-direct physical injury or death caused solely by defects in the software
-unless it is modified by a third party.]
-
-THIS SOFTWARE IS PROVIDED BY THE AUTHORS ``AS IS'' AND ANY EXPRESS OR
-IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
-WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
-DISCLAIMED. IN NO EVENT SHALL THE AUTHORS BE LIABLE FOR ANY DIRECT,
-INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
-(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
-SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
-HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
-STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN
-ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
-POSSIBILITY OF SUCH DAMAGE.
-</pre>
-
-<h2>Commentary</h2>
-
-<p>This license is based on a standard BSD license. Some minor changes
-in wording have been made to fit in with English law.</p>
-
-<p> </p>
-<p>© Ben Summers, 2003, 2004</p>
-<p> </p>
-</div>
-</div>
-</body>
-</html>
\ No newline at end of file
Deleted: trunk/dports/sysutils/boxbackup/files/nonroot.html
===================================================================
--- trunk/dports/sysutils/boxbackup/files/nonroot.html 2009-01-29 19:52:24 UTC (rev 46111)
+++ trunk/dports/sysutils/boxbackup/files/nonroot.html 2009-01-29 20:13:19 UTC (rev 46112)
@@ -1,56 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml">
-<head>
-<meta http-equiv="content-type" content="text/html;charset=iso-8859-1" />
-<title>Running without root</title>
-<link rel="stylesheet" href="bbstyles.css" type="text/css" />
-</head>
-<body>
-<div align="center">
-<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>
-<div id="page">
-
-<h1>Running without root</h1>
-
-<p>It is possible to run both the server and client without root privileges.</p>
-
-<h2>Server</h2>
-
-<p>The server, by default, runs as a non-root user. However, it expects to be run as root
-and changes user to a specified user as soon as it can, simply for administrative convenience.
-The server uses a port greater than 1024, so it doesn't need root to start.</p>
-
-<p>To run it entirely as a non-root user, edit the <tt>bbstored.conf</tt> file, and remove the
-<tt>User</tt> directive from the <tt>Server</tt> section. Then simply run the server as your
-desired user.</p>
-
-<h2>Client</h2>
-
-<p>The client requires root for normal operation, since it must be able to access all files
-to back them up. However, it is possible to run the client as a non-root user, with certain
-limitations.</p>
-
-<p>Follow the installation instructions, but install the executable files manually to somewhere
-in your home directory. Then use <tt>bbackupd-config</tt> to configure the daemon, but use a
-directory other than <tt>/etc/box</tt>, probably somewhere in your home directory.</p>
-
-<p>All directories you specify to be backed up must be readable, and all files must be owned
-by the user and readable to that user.</p>
-
-<p><b>Important:</b> If any file or directory is not readable by this user, the backup process
-will skip that file or directory. Keep an eye on the logs for reports of this failure.</p>
-
-<p>Non-root operation of the backup client is recommended only for testing, and should not
-be relied on in a production environment.</p>
-
-<p> </p>
-<p>© Ben Summers, 2003, 2004</p>
-<p> </p>
-</div>
-</div>
-</body>
-</html>
Deleted: trunk/dports/sysutils/boxbackup/files/patch-BoxPlatform.pm.in.diff
===================================================================
--- trunk/dports/sysutils/boxbackup/files/patch-BoxPlatform.pm.in.diff 2009-01-29 19:52:24 UTC (rev 46111)
+++ trunk/dports/sysutils/boxbackup/files/patch-BoxPlatform.pm.in.diff 2009-01-29 20:13:19 UTC (rev 46112)
@@ -1,14 +0,0 @@
---- infrastructure/BoxPlatform.pm.in.org 2006-02-23 12:47:36.000000000 -0800
-+++ infrastructure/BoxPlatform.pm.in 2006-03-22 23:29:51.000000000 -0800
-@@ -41,6 +41,11 @@
- # if it's Darwin,
- if($build_os eq 'Darwin')
- {
-+ # Use headers and libraries from Darwinports
-+ $platform_compile_line_extra = '-I__PREFIX__/include ';
-+ $platform_link_line_extra = '-L__PREFIX__/lib ';
-+
-+
- # see how many processors there are, and set make flags accordingly
- my $cpus = `sysctl hw.ncpu`;
- if($cpus =~ m/hw.ncpu:\s(\d+)/ && $1 > 1)
Deleted: trunk/dports/sysutils/boxbackup/files/restore.html
===================================================================
--- trunk/dports/sysutils/boxbackup/files/restore.html 2009-01-29 19:52:24 UTC (rev 46111)
+++ trunk/dports/sysutils/boxbackup/files/restore.html 2009-01-29 20:13:19 UTC (rev 46112)
@@ -1,109 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml">
-<head>
-<meta http-equiv="content-type" content="text/html;charset=iso-8859-1" />
-<title>Box Backup verify and restore files</title>
-<link rel="stylesheet" href="bbstyles.css" type="text/css" />
-</head>
-<body>
-<div align="center">
-<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>
-<div id="page">
-
-<h1>Box Backup verify and restore files</h1>
-
-<p>Backups are no use unless you can restore them. The <tt>bbackupquery</tt> utility does
-this and more.</p>
-
-<p>You don't provide any login information to it, as it just picks up the data it needs
-from <tt>/etc/box/bbackupd.conf</tt>. You should run it as root so it can find everything
-it needs.</p>
-
-<p>Full documentation can be found in <tt>bin/bbackupquery/documentation.txt</tt> in the distribution
-archive. It follows the model of a command line sftp client quite closely.</p>
-
-<p>On systems where GNU readline is available (by default) it uses that for command line history and
-editing. Otherwise it falls back to very basic UNIX text entry.</p>
-
-
-<h2>Verify backups</h2>
-
-<p>Since this is a development system, you'll be keen to verify that your backups are
-correct. This is easy.</p>
-
-<pre>
-/usr/local/bin/bbackupquery "compare -a" quit
-</pre>
-
-<p>It will report all the differences between the store and the files on disc. It will download
-everything, so may take a while. You should expect to see some differences on a typical compare,
-because files which have recently changed are unlikely to have been uploaded yet. Consider checking the
-timestamps on the files, or keeping a record of these messages and comparing them with a future verification.</p>
-
-<p>If you would like to do a "quick" check which just downloads file
-checksums and compares against that, then do</p>
-
-<pre>
-/usr/local/bin/bbackupquery "compare -aq" quit
-</pre>
-
-<p>However, this does not check that the file attributes are correct, and since the checksums are generated
-on the client they may not reflect the data on the server if there is a problem -- the server cannot check
-the encrypted contents. View this as a good indication, rather than a definite check that your backup
-verifies correctly.</p>
-
-<p>You may wish to run either one as a cron job while testing this system.</p>
-
-
-<h2>Restore backups</h2>
-
-<p>You will need the keys file created when you configured the server. Without it, <b>you cannot
-restore the files</b>; this is the downside of encrypted backups. However, by keeping the small
-keys file safe, you indirectly keep your entire backup safe.</p>
-
-<p>The first step is to recreate the configuration of the backup client. It's probably best
-to have stored the /etc/box directory with your keys. But if you're recreating it, all you really
-need is to have got the login infomation correct (ie the certs and keys).</p>
-
-<p><b>Don't run bbackupd yet!</b> It will mark all your files as deleted if you do, which is not
-hugely bad in terms of losing data, just a major inconvenience. (This assumes that
-you are working from a blank slate. If you want to restore some files to a different location,
-it's fine to restore while bbackupd is running, just do it outside a backed up directory to make
-sure it doesn't start uploading the restored files.)</p>
-
-<p>Type <tt>/usr/local/bin/bbackupquery</tt> to run it in interactive mode.</p>
-
-<p>Type <tt>list</tt> to see a list of the locations stored on the server.</p>
-
-<p>For each location you want to restore, type <tt>restore name-on-server local-dir-name</tt>. The
-directory specified by local-dir-name must not exist yet.</p>
-
-<p>If the restore is interrupted for any reason, repeat the above steps, but add the <tt>-r</tt>
-flag to the restore command to tell it to resume.</p>
-
-
-<h2>Other tricks</h2>
-
-<p>bbackupquery can also...
-<ul>
-<li>List files on the server
-<li>Restore arbitary parts of the file system
-<li><a href="retrieve.html">Recover deleted files</a> (either if the backup daemon hasn't deleted them from the store,
-or if they are marked on the store as deleted but not actually gone yet.)
-<li><a href="retrieve.html">Recover old versions</a> of files which are still on the server.
-</ul>
-</p>
-
-<p>Read <tt>bin/bbackupquery/documentation.txt</tt> for more details.</p>
-
-<p> </p>
-<p>© Ben Summers, 2003, 2004</p>
-<p> </p>
-</div>
-</div>
-</body>
-</html>
\ No newline at end of file
Deleted: trunk/dports/sysutils/boxbackup/files/retrieve.html
===================================================================
--- trunk/dports/sysutils/boxbackup/files/retrieve.html 2009-01-29 19:52:24 UTC (rev 46111)
+++ trunk/dports/sysutils/boxbackup/files/retrieve.html 2009-01-29 20:13:19 UTC (rev 46112)
@@ -1,93 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml">
-<head>
-<meta http-equiv="content-type" content="text/html;charset=iso-8859-1" />
-<title>Retrieving deleted and old files</title>
-<link rel="stylesheet" href="bbstyles.css" type="text/css" />
-</head>
-<body>
-<div align="center">
-<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>
-<div id="page">
-
-<h1>Retrieving deleted and old files</h1>
-
-<p>Box Backup makes old versions of files and files you have deleted available, subject to there
-being enough disc space on the server to hold them.</p>
-
-<p>This is how to retrieve them using <tt>bbackupquery</tt>. Future versions will make this far
-more user-friendly.</p>
-
-<p>Firstly, run <tt>bbackupquery</tt> in interactive mode. It behaves in a similar manner to
-a command line sftp client.</p>
-
-<pre>
-/usr/local/bin/bbackupquery
-</pre>
-
-<p>Then navigate to the directory containing the file you want, using <tt>list</tt>, <tt>cd</tt>
-and <tt>pwd</tt>.</p>
-
-<pre>
-query > cd home/profiles/USERNAME
-</pre>
-
-<p>List the directory, using the "o" option to list the files available without filtering out
-everything apart from the current version. (if you want to see deleted files as well, use
-<tt>list -odt</tt>)</p>
-
-<pre>
-query > list -ot
-00000078 f--o- 2004-01-21T20:17:48 NTUSER.DAT
-00000079 f--o- 2004-01-21T20:17:48 ntuser.dat.LOG
-0000007a f--o- 2004-01-21T17:55:12 ntuser.ini
-0000007b f---- 2004-01-12T15:32:00 ntuser.pol
-0000007c -d--- 1970-01-01T00:00:00 Templates
-00000089 -d--- 1970-01-01T00:00:00 Start Menu
-000000a0 -d--- 1970-01-01T00:00:00 SendTo
-000000a6 -d--- 1970-01-01T00:00:00 Recent
-00000151 -d--- 1970-01-01T00:00:00 PrintHood
-00000152 -d--- 1970-01-01T00:00:00 NetHood
-00000156 -d--- 1970-01-01T00:00:00 My Documents
-0000018d -d--- 1970-01-01T00:00:00 Favorites
-00000215 -d--- 1970-01-01T00:00:00 Desktop
-00000219 -d--- 1970-01-01T00:00:00 Cookies
-0000048b -d--- 1970-01-01T00:00:00 Application Data
-000005da -d--- 1970-01-01T00:00:00 UserData
-0000437e f--o- 2004-01-24T02:45:43 NTUSER.DAT
-0000437f f--o- 2004-01-24T02:45:43 ntuser.dat.LOG
-00004380 f--o- 2004-01-23T17:01:29 ntuser.ini
-00004446 f--o- 2004-01-24T02:45:43 NTUSER.DAT
-00004447 f--o- 2004-01-24T02:45:43 ntuser.dat.LOG
-000045f4 f---- 2004-01-26T15:54:16 NTUSER.DAT
-000045f5 f---- 2004-01-26T15:54:16 ntuser.dat.LOG
-000045f6 f---- 2004-01-26T16:54:31 ntuser.ini
-</pre>
-
-<p>(this is a listing from a server which is used as a Samba server for a network of
-Windows clients.)</p>
-
-<p>You now need to fetch the file using it's ID, rather than it's name. The ID is the
-hex number in the first column. Fetch it like this:</p>
-
-<pre>
-query > get -i 0000437e NTUSER.DAT
-Object ID 0000437e fetched successfully.
-</pre>
-
-<p>The object is now available on your local machine. You can use <tt>lcd</tt> to move
-around, and <tt>sh ls</tt> to list directories on your local machine.</p>
-
-<p> </p>
-<p>© Ben Summers, 2003, 2004</p>
-<p> </p>
-</div>
-</div>
-</body>
-</html>
-
-
Deleted: trunk/dports/sysutils/boxbackup/files/server.html
===================================================================
--- trunk/dports/sysutils/boxbackup/files/server.html 2009-01-29 19:52:24 UTC (rev 46111)
+++ trunk/dports/sysutils/boxbackup/files/server.html 2009-01-29 20:13:19 UTC (rev 46112)
@@ -1,215 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml">
-<head>
-<meta http-equiv="content-type" content="text/html;charset=iso-8859-1" />
-<title>Box Backup server configuration</title>
-<link rel="stylesheet" href="bbstyles.css" type="text/css" />
-</head>
-<body>
-<div align="center">
-<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>
-<div id="page">
-
-<h1>Box Backup server configuration</h1>
-
-<h2>Log files</h2>
-
-<p>You may wish to see what's going on with the server. Edit /etc/syslog.conf, and add</p>
-
-<pre>
-local6.info /var/log/box
-local5.info /var/log/raidfile
-</pre>
-
-<p>Note separators must be tabs, otherwise it ignores you.</p>
-
-<pre>
-touch /var/log/box
-touch /var/log/raidfile
-</pre>
-
-<p>And then get them rotated, by adding in /etc/newsyslog.conf</p>
-
-<pre>
-/var/log/box 644 7 2000 * Z
-/var/log/raidfile 644 7 2000 * Z
-</pre>
-
-<p>Then restart syslogd.</p>
-
-<h2>RAID setup</h2>
-
-<p>The server does RAID in userland for that extra bit of reliability. You need to
-set this up separately from the server. To create <tt>/etc/box/raidfile.conf</tt>,</p>
-
-<pre>
-/usr/local/bin/raidfile-config /etc/box 2048 /raid/0.0 /raid/0.1 /raid/0.2
-</pre>
-
-<p>But adjust it for your system. 2048 is the block size. Under BSD with FFS, set this to
-your filing system's fragment size (most likely an 8th of the block size), otherwise the block size of
-the filing system, for maximum efficiency.</p>
-
-<p>The three directories are the locations of the roots of the raid file directories.
-These are probably the mount points of three big partitions on three <b>separate physical discs</b>.
-If you don't have this, see below on how to disable userland RAID.</p>
-
-<p>Edit <tt>/etc/box/raidfile.conf</tt> if you have another set of three discs you want
-to use -- just add another section for each set.</p>
-
-<h3>Disabling userland RAID</h3>
-
-<p>If you only have one disc, or a hardware RAID array, you probably won't want to use userland
-RAID.</p>
-
-<p>In this case, follow the above instructions, but only specify one directory for the
-<tt>raidfile-config</tt> script. This will generate a raidfile.conf which disables userland
-RAID, and stores files in the single directory you specify.</p>
-
-<p><b>NOTE</b> Running the server in non-RAID mode has not been tested as extensively as
-in RAID file mode.</p>
-
-
-<h2>Server basic setup</h2>
-
-<p>Create a user to run the server under:</p>
-
-<pre>
-useradd _bbstored
-</pre>
-
-<p>Create <tt>/etc/box/bbstored.conf</tt> with:</p>
-
-<pre>
-/usr/local/bin/bbstored-config /etc/box <b>hostname</b> _bbstored
-</pre>
-
-<p>(See <a href="openssl.html">OpenSSL notes</a> if you get an OpenSSL error)</p>
-
-<p>(set hostname to the address the clients
-will use to contact this server) <b>Are you using a NAT device or firewall?</b> See the note below.</p>
-
-<p><b>Read the output</b> for details of what to do next. There is an example at the end of this page,
-but do follow the instructions output when you run the script yourself.</p>
-
-<p>Make sure the user can write to the raid file directories! For more precise control,
-create a <tt>backup</tt> directory within each of the raid root directories, and change
-their permissions accordingly.</p>
-
-<p>If there are other users on this server, you will probably want to stop other users
-reading the certificates.</p>
-
-<pre>
-chown -R _bbstored /etc/box/bbstored
-chmod -R go-rwx /etc/box/bbstored
-</pre>
-
-<h2>Configuration for hosts behind a NAT device or firewall</h2>
-
-<p>The hostname specified is used for 1) the name in the server's certificate and 2) the
-address the server will listen on.</p>
-
-<p>If the IP address of the machine isn't the same as the IP address it appears to have to
-the outside world (because the NAT device or firewall translates it), then this will fail.
-The server will look up the hostname, and then fail to bind to that address since it is not a local
-address.</p>
-
-<p>To get around this, you have two options. Either specify the local IP address with the
-<tt>bbstored-config</tt> command (the name in the certificate won't match the real address, but
-this is not a problem at the moment), or specify the real address, but edit the <tt>bbstored.conf</tt>
-file and correct the <tt>ListenAddresses</tt> directive later to reflect the local address.</p>
-
-<h2>Get certified</h2>
-
-<p>As per the instructions in the <a href="accounts.html">certificates and accounts management</a> page,
-sign your certificate and install it as directed.</p>
-
-<h2>Start the server</h2>
-
-<pre>
-/usr/local/bin/bbstored
-</pre>
-
-<p>Add this to your system startup scripts.</p>
-
-<p>Please read the <a href="trouble.html">Troubleshooting</a> page if you have problems.</p>
-
-<p>If you configured the server so the configuration file is somewhere other than <tt>/etc/box/bbstored.conf</tt>,
-run the server as, for example,<p>
-
-<pre>
-/usr/local/bin/bbstored /some/other/config/dir/bbstored.conf
-</pre>
-
-<h2>root not required</h2>
-
-<p>The backup server is configured to be run as root, but changes user to the user
-you specify as soon as it can -- this is simply for convenience when starting the daemon
-in system start up scripts. However, you can <a href="nonroot.html">run without root</a>
-entirely by making a small change to the configuration file.</p>
-
-
-<h2>Example configuration output</h2>
-
-<p>This is an example of output from the bbstored-config script. <b>Important:</b>
-Follow the instructions output by your script, not the ones here -- they may be different
-for your system.</p>
-
-<pre>
-# /usr/local/bin/bbstored-config /etc/box server.example.com _bbstored
-Checking permissions on /raid/0.0/backup
-Checking permissions on /raid/0.1/backup
-Checking permissions on /raid/0.2/backup
-
-Setup bbstored config utility.
-
-Configuration:
- Writing configuration file: /etc/box/bbstored.conf
- Writing empty accounts file: /etc/box/bbstored/accounts.txt
- Server hostname: server.example.com
- RaidFile config: /etc/box/raidfile.conf
-
-Creating /etc/box/bbstored
-Creating blank accounts file
-Generating private key...
- [OpenSSL output omitted]
-
-Writing configuration file /etc/box/bbstored.conf
-
-===================================================================
-
-bbstored basic configuration complete.
-
-What you need to do now...
-
-1) Sign /etc/box/bbstored/server.example.com-csr.pem
- using the bbstored-certs utility.
-
-2) Install the server certificate and root CA certificate as
- /etc/box/bbstored/server.example.com-cert.pem
- /etc/box/bbstored/clientCA.pem
-
-3) You may wish to read the configuration file
- /etc/box/bbstored.conf
- and adjust as appropraite.
-
-4) Create accounts with bbstoreaccounts
-
-5) Start the backup store daemon with the command
- /usr/local/bin/bbstored
- in /etc/rc.local, or your local equivalent.
-
-===================================================================
-</pre>
-
-<p> </p>
-<p>© Ben Summers, 2003, 2004</p>
-<p> </p>
-</div>
-</div>
-</body>
-</html>
\ No newline at end of file
Deleted: trunk/dports/sysutils/boxbackup/files/serverfix.html
===================================================================
--- trunk/dports/sysutils/boxbackup/files/serverfix.html 2009-01-29 19:52:24 UTC (rev 46111)
+++ trunk/dports/sysutils/boxbackup/files/serverfix.html 2009-01-29 20:13:19 UTC (rev 46112)
@@ -1,105 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml">
-<head>
-<meta http-equiv="content-type" content="text/html;charset=iso-8859-1" />
-<title>Fixing problems with corruption on the server</title>
-<link rel="stylesheet" href="bbstyles.css" type="text/css" />
-</head>
-<body>
-<div align="center">
-<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>
-<div id="page">
-
-<h1>Fixing problems with corruption on the server</h1>
-
-<p>This page gives help on what to do if your server has suffered corruption, for example,
-after an unclean shutdown or other OS or hardware problem.</p>
-
-<p>In general, as updates to the store are made in an atomic manner, the most
-likely result is wasted disc space. However, if really bad things happen, or you believe that
-there is a lot of wasted space, then these instructions will help to restore your data.</p>
-
-<p>You know you will need to do something if you get strange errors, and <tt>bbackupd</tt> attempts
-to contact the server every 100 seconds or so. Or if one of the discs in your RAID disc set has failed.</p>
-
-<p>After following these instructions, the end result will be that <tt>bbackupquery</tt> will be able to see all the files which
-were stored on your server, and retrieve them. Some of them may be in <tt>lost+found</tt>
-directories in the root of the store (or in their original position if they have been moved) but they will all
-be able to be retrieved.</p>
-
-<p>After you have retrieved the files you want, <tt>bbackupd</tt> will upload new versions
-where necessary, and after about two days, mark any <tt>lost+found</tt> directories as deleted.
-Finally, those directories will be removed by the housekeeping process on the server.</p>
-
-<p>These instructions assume you're working on account 1234, subsitute this for whatever account
-you're actually working on. These will need to be repeated for all affected accounts.</p>
-
-<h2>1. Stop bbackupd</h2>
-
-<p>First, make sure that <tt>bbackupd</tt> is not running on the client machine for the account
-you are going to recover. Use <tt>kill</tt> to terminate it.</p>
-
-<p>(This step is not strictly necessary, but is recommended. During any checks on the account,
-<tt>bbackupd</tt> will be unable to log in, and after they are complete, the account is marked
-as changed on the server so <tt>bbackupd</tt> will perform a complete scan.)</p>
-
-<h2>2. Are you using RAID on the server?</h2>
-
-<p>At the moment, the raidfile recovery tools have not been written. However, when two out of
-three files are available, the server will run succesfully, even if it complains a lot in the logs.
-So, your best bet here is to fix the accounts, if necessary, and retrieve any files you need. Then move
-the old store directories aside (in case you need them) and start afresh with new accounts, and
-let the clients upload all their data again.</p>
-
-<p>These utilities will be written shortly!</p>
-
-<h2>3. Check and fix the account</h2>
-
-<p>First, run the check utility, and see what errors it reports.</p>
-
-<pre>
- /usr/local/bin/bbstoreaccounts check 1234
-</pre>
-
-<p>This will take some time, and use a fair bit of memory (about 16 bytes per file and directory).
-If the output looks plausible and reports errors which need fixing, run it again but with the
-<tt>fix</tt> flag:</p>
-
-<pre>
- /usr/local/bin/bbstoreaccounts check 1234 fix
-</pre>
-
-<p>This will fix any errors, and remove unrecoverable files. Directories will be recreated if necessary.</p>
-
-<p><b>NOTE</b>: The utility may adjust the soft and hard limits on the account to make sure that
-housekeeping will not remove anything -- check these afterwards.</p>
-
-<h2>4. Grab any files you need with bbackupquery</h2>
-
-<p>At this point, you will have a working store. Every file which was on the server, and wasn't corrupt,
-will be available.<p>
-
-<p>On the client, use <tt>bbackupquery</tt> to log in and examine the store. (type <tt>help</tt> at the
-prompt for instructions). Retrieve any files you need, paying attention to any <tt>lost+found</tt>
-directories in the root directory of the store.</p>
-
-<p>You can skip this step if you are sure that the client machine is fine -- in this case, <tt>bbackupd</tt>
-will bring the store up to date.</p>
-
-<h2>5. Restart bbackupd</h2>
-
-<p>Restart <tt>bbackupd</tt> on the client machine. The store account will be brought up to date, and
-files in the wrong place will be marked for eventual deletion.</p>
-
-
-<p> </p>
-<p>© Ben Summers, 2003, 2004</p>
-<p> </p>
-</div>
-</div>
-</body>
-</html>
Deleted: trunk/dports/sysutils/boxbackup/files/space.html
===================================================================
--- trunk/dports/sysutils/boxbackup/files/space.html 2009-01-29 19:52:24 UTC (rev 46111)
+++ trunk/dports/sysutils/boxbackup/files/space.html 2009-01-29 20:13:19 UTC (rev 46112)
@@ -1,56 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml">
-<head>
-<meta http-equiv="content-type" content="text/html;charset=iso-8859-1" />
-<title>Checking the storage space used on the server</title>
-<link rel="stylesheet" href="bbstyles.css" type="text/css" />
-</head>
-<body>
-<div align="center">
-<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>
-<div id="page">
-
-<h1>Checking the storage space used on the server</h1>
-
-<h2>From the machine being backed up</h2>
-
-<p><tt>bbackupquery</tt> can tell you how much space is used on the server for this account.</p>
-
-<p>Either use the <tt>usage</tt> command in interactive mode, or type</p>
-
-<pre>
- /usr/local/bin/bbackupquery -q usage quit
-</pre>
-
-<p>to show the space used as a single command.</p>
-
-
-<h2>On the server</h2>
-
-<p><tt>bbstoreaccounts</tt> allows you to query the space used, and change the limits.
-To display the space used on the server for an account, use</p>
-
-<pre>
- /usr/local/bin/bbstoreaccounts info 75AB23C
-</pre>
-
-<p>To adjust the soft and hard limits on an account, use</p>
-
-<pre>
- /usr/local/bin/bbstoreaccounts setlimit 75AB23C new-soft-limit new-hard-limit
-</pre>
-
-<p>You do not need to restart the server.</p>
-
-
-<p> </p>
-<p>© Ben Summers, 2003, 2004</p>
-<p> </p>
-</div>
-</div>
-</body>
-</html>
Deleted: trunk/dports/sysutils/boxbackup/files/trouble.html
===================================================================
--- trunk/dports/sysutils/boxbackup/files/trouble.html 2009-01-29 19:52:24 UTC (rev 46111)
+++ trunk/dports/sysutils/boxbackup/files/trouble.html 2009-01-29 20:13:19 UTC (rev 46112)
@@ -1,122 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml">
-<head>
-<meta http-equiv="content-type" content="text/html;charset=iso-8859-1" />
-<title>Troubleshooting Box Backup</title>
-<link rel="stylesheet" href="bbstyles.css" type="text/css" />
-</head>
-<body>
-<div align="center">
-<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>
-<div id="page">
-
-<h1>Troubleshooting Box Backup</h1>
-
-<p><ul><li><b>Note</b>: If you are trying to fix a store after your disc has been corrupted, see
-<a href="serverfix.html">fixing problems with corruption on the server</a>.</ul></p>
-
-<p>Unfortunately, the error messages are not particularly helpful at the moment. This page lists
-some of the common errors, and the most likely causes of them.</p>
-
-<p>When an error occurs, you will see a message like '<tt>Exception: RaidFile/OSFileError (2/8)</tt>' either
-on the screen or in your log files. (it is recommended you set up another log file as recommended
-in the <a href="server.html">server setup instructions</a>.)</p>
-
-<p>This error may not be particularly helpful, although some do have extra information about probable causes.
-To get further information, check the <tt>ExceptionCodes.txt</tt> file in the root of the distribution.
-This file is generated by the <tt>./configure</tt> script, so you will need to have run that first.</p>
-
-<p>Some common causes of exceptions are listed below.</p>
-
-<p>Please email me with any other codes you get, and I will let you know what they mean, and add
-notes here.</p>
-
-
-<h2>RaidFile (2/8)</h2>
-
-<p>This is found either when running <tt>bbstoreaccounts</tt> or in the <tt>bbstored</tt> logs.</p>
-
-<p><b>Problem:</b> The directories you specified in the raidfile.conf are not writable by the _bbstored user.</p>
-
-<p><b>Resolution:</b> Change permissions appropriately.</p>
-
-
-<h2>Common (1/2)</h2>
-
-<p>This usually occurs when the configuration files can't be opened.</p>
-
-<p><b>Problem:</b> You created your configurations in non-standard locations, and the programs
-cannot find them.</p>
-
-<p><b>Resolution:</b> Explicitly specify configuration file locations to daemons and programs. For example</p>
-<pre>
-/usr/local/bin/bbstored /some/other/dir/bbstored.config
-/usr/local/bin/bbackupquery -c /some/other/dir/bbackupd.config
-</pre>
-<p>(daemons specify the name as the first argument, utility programs with the <tt>-c</tt> option.</p>
-
-<p><b>Problem:</b> <tt>bbstored</tt> can't find the <tt>raidfile.conf</tt> file specified in <tt>bbstored.conf</tt>.</p>
-
-<p><b>Resolution:</b> Edit <tt>bbstored.conf</tt> to point to the correct location of this additional configuration file.</p>
-
-
-<h2>Server (3/16)</h2>
-
-<p>The server can't listen for connections on the IP address specified when you configured it.</p>
-
-<p><b>Problem:</b> This probably means you've specified the wrong hostname to bbstored-config --
-maybe your server is behind a NAT firewall?</p>
-
-<p><b>Resolution:</b> Edit <tt>bbstored.conf</tt> and correct the <tt>ListenAddresses</tt> line. You
-should replace the server address with the IP address of your machine.</p>
-
-
-<h2>Connection (7/x)</h2>
-
-<p>These errors all relate to connections failing -- you may see them during operation if there
-are network failures or other problems between the client and server. The backup system will recover
-from them automatically.</p>
-
-
-<p> </p>
-
-<h1>Advanced troubleshooting</h1>
-
-<p>If this really doesn't help, then using the DEBUG builds of the system will give you much more
-information -- a more descriptive exception message and the file and line number where the error occurred.</p>
-
-<p>For example, if you are having problems with <tt>bbstoreaccounts</tt>, build the debug version with</p>
-
-<pre>
-cd boxbackup-0.0
-cd bin/bbstoreaccounts
-make
-</pre>
-
-<p>(within the module directories, <tt>make</tt> defaults to building the debug version. At the top level,
-it defaults to release.)</p>
-
-<p>This will build an executable in <tt>debug/bin/bbstoreaccounts</tt> which you can then use instead
-of the release version. It will give far more useful error messages.</p>
-
-<p>When you get an error message, use the file and line number to locate where the error occurs in the
-code. There will be comments around that line to explain why the exception happened.</p>
-
-<p>If you are using a debug version of a daemon, these extended messages are found in the log files.</p>
-
-<p>Please get in touch if you need any help.</p>
-
-<p> </p>
-<p>© Ben Summers, 2003, 2004</p>
-<p> </p>
-</div>
-</div>
-</body>
-</html>
-
-
-
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-changes/attachments/20090129/24ae9361/attachment-0001.html>
More information about the macports-changes
mailing list