Nicki,

The next amanda version will understand tar returning 1.
You can already use the latest snapshot or CVS.

Jean-Louis

Nicki Messerschmidt, Linksystem Muenchen GmbH wrote:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,
another problem with my backup with debian testing as a client was tar
1.16.
In this new version tar exits with error code 1 (TAR_FILECHANGED) if any
file changed during backup. In tar 1.15 it only exited with error code 2
if a file was truncated during backup.
With this new behavior backup of partitions containing log files is
hardly doable.
For now I downgraded to tar 1.15.
Is there any possibility for amanda to honor this new tar behavior?

- From the NEWS file of the tar source package:
version 1.16 - Sergey Poznyakoff, 2006-10-21

* After creating an archive, tar exits with code 1 if some files were
changed while being read.  Previous versions exited with code 2 (fatal
error), and only if some files were truncated while being archived.



Cheers
Nicki

- --
Linksystem Muenchen GmbH                          info AT link-m DOT de
Schloerstrasse 10                           http://www.link-m.de
80634 Muenchen                              Tel. 089 / 890 518-0
We make the Net work.                       Fax 089 / 890 518-77
PGP Keys:                             https://www.link-m.de/pgp/

- --
Linksystem Muenchen GmbH                          info AT link-m DOT de
Schloerstrasse 10                           http://www.link-m.de
80634 Muenchen                              Tel. 089 / 890 518-0
We make the Net work.                       Fax 089 / 890 518-77
PGP Keys:                             https://www.link-m.de/pgp/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (MingW32)
Comment: Get keys at: https://www.link-m.de/pgp

iD8DBQFFpNEa6zWc+bXuIEMRAszDAJ9+Pi6vwEbPKViCp7K9UijR+YRJmQCg/i7p
mg/jvokefoSS2q1NPIGFfgc=
=kLvK
-----END PGP SIGNATURE-----