From d1c113ccf99adff705a6da4ba9e776fbeacaef92 Mon Sep 17 00:00:00 2001 From: Dan Scott Date: Mon, 7 Nov 2011 16:38:32 -0500 Subject: [PATCH] Backup the existing opensrf config files before copying Per a suggestion from Wolf Halton , create backup versions of the opensrf configuration files when we're copying the Evergreen example versions over, so that we can retrieve the Jabber user names and passwords and domains from the backups (if necessary). Signed-off-by: Dan Scott --- README | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/README b/README index b6dbe708ff..d42c97aee3 100644 --- a/README +++ b/README @@ -277,8 +277,8 @@ following commands as the *opensrf* Linux account: [source, bash] ------------------------------------------------------------------------------ -cp /openils/conf/opensrf_core.xml.example /openils/conf/opensrf_core.xml -cp /openils/conf/opensrf.xml.example /openils/conf/opensrf.xml +cp -b /openils/conf/opensrf_core.xml.example /openils/conf/opensrf_core.xml +cp -b /openils/conf/opensrf.xml.example /openils/conf/opensrf.xml ------------------------------------------------------------------------------ When you installed OpenSRF, you created four Jabber users on two @@ -287,6 +287,12 @@ refer back to the OpenSRF README and, as the *opensrf* Linux account, edit the Evergreen version of the `opensrf_core.xml` file using the same Jabber users and domains as you used while installing and testing OpenSRF. +[NOTE] +The `-b` flag tells the `cp` command to create a backup version of the +destination file. The backup version of the destination file has a tilde (`~`) +appended to the file name, so if you have forgotten the Jabber users and +domains, you can retrieve the settings from the backup version of the files. + `eg_db_config.pl`, described in the following section, sets the database connection information in `opensrf.xml` for you. -- 2.43.2