Made the copy of the .conf files to /etc/gnumed and made a backup (very long name.tar)
Then after trying to run the restore script gives:
file: /home/rogerio/Desktop/backup-gnumed_v9-GNUmed_Team-casa-deb-2008-10-15-21-19-03-data_only.tar
==> Reading configuration ...
file: /etc/gnumed/gnumed-restore.conf
==> Testing backup file integrity ...
/home/rogerio/Desktop/backup-gnumed_v9-GNUmed_Team-casa-deb-2008-10-15-21-19-03-data_only.tar: bad magic number (file not created by bzip2)
You can use the `bzip2recover' program to attempt to recover
data from undamaged sections of corrupted files.
ERROR: integrity check failed, aborting
Please advise
Rogerio
2008/10/12 Karsten Hilbert
<address@hidden>
> Subject: Re: [Gnumed-devel] BACKUP / RESTORE
> User-Agent: Mutt/1.5.18 (2008-05-17)
>
> On Fri, Oct 03, 2008 at 05:03:50PM -0300, Rogerio Luz wrote:
>
> > When I try the gm-backup_database.sh , even as root, it says that a file
> > called etc/gnumed/gnumed-bacckup.conf is missing and it aborts ...
>
> It aborts because it is missing its configuration file.
> There is an example in the tarball/in the CVS.
>
> Karsten
> --
> GPG key ID E4071346 @ wwwkeys.pgp.net
> E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346
--
GPG key ID E4071346 @ wwwkeys.pgp.net
E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346