|
From: <di...@us...> - 2007-03-08 20:56:13
|
Revision: 447
http://safekeep.svn.sourceforge.net/safekeep/?rev=447&view=rev
Author: dimi
Date: 2007-03-08 12:56:12 -0800 (Thu, 08 Mar 2007)
Log Message:
-----------
Update docs
Modified Paths:
--------------
safekeep/trunk/doc/safekeep.backup.txt
Modified: safekeep/trunk/doc/safekeep.backup.txt
===================================================================
--- safekeep/trunk/doc/safekeep.backup.txt 2007-03-08 20:53:35 UTC (rev 446)
+++ safekeep/trunk/doc/safekeep.backup.txt 2007-03-08 20:56:12 UTC (rev 447)
@@ -114,11 +114,10 @@
/backup/repo/@path::
The path under which the backups will be stored. Relative
- paths are based on current working directory where `safekeep(1)`
- server is run. Typically this working directory will be the home
- directory of the user under which `safekeep(1)` runs on the server.
- As a result, in a typical installation the data will be stored
- under `/var/lib/safekeep/<id>/`. If the directory does not exist,
+ paths are based on the 'base.dir' setting from the 'safekeep.conf(5)'.
+ Since the default value for 'base.dir' is the user's home directory,
+ in a typical installation the data will be stored under
+ `/var/lib/safekeep/<id>/`. If the directory does not exist,
`safekeep(1)` will attempt to create it automatically. The backup
will fail altogether if the directory can not be created.
Optional, defaults to the client ID, see `/backup/@id`.
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|