[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Gnumed-bugs] Problems restoring from a backup - directory ... does
From: |
Busser, Jim |
Subject: |
Re: [Gnumed-bugs] Problems restoring from a backup - directory ... does not exist |
Date: |
Thu, 15 Jan 2015 15:32:27 +0000 |
On 2015-01-14, at 2:57 AM, Karsten Hilbert <address@hidden> wrote:
> Please post content of "/etc/gnumed/gnumed-restore.conf".
>
>> ==> Setting up workspace ...
>> Users/djb/gnumed/gm-restore-2015-01-13-10-27-04
>
> Given that the workspace name does NOT start with a "/" I
> would suspect the option WORK_DIR_BASE inside
> /etc/gnumed/gnumed-restore.conf does not start with one
> either ?
Ah, good catch … in my
gnumed-backup.conf
I have
...
# where to eventually store the backup
# BACKUP_DIR="${HOME}/.gnumed/backup/"
BACKUP_DIR="/Users/djb/.gnumed/backup/"
whereas in
gnumed-restore.conf
I had indeed left out the leading /
…
# set this to a writable directory on a drive where
# there is plenty of disk space available
# WORK_DIR_BASE="${HOME}/gnumed"
WORK_DIR_BASE="Users/djb/gnumed"
prompting the question whether it is intended or recommended that WORK_DIR_BASE
be set to be a fully specified, absolute path or whether some people can
perfectly well leave it the default
WORK_DIR_BASE="${HOME}/gnumed"
and if it might simply be that I had a Mac related problem (maybe even just
$PATH related) whose workaround solution for me had been to opt for an absolute
path.
-- Jim