On Wed, Jun 21, 2006 at 11:11:36AM -0400, Jon LaBadie wrote: > > > > Looking at the log files, I see a typical runtar log as follows: > > > > -------------------------------------------------- > > runtar: debug 1 pid 6507 ruid 33 euid 0: start at Wed Jun 21 08:24:02 2006 > > /bin/tar: version 2.4.5p1 > > running: /bin/tar: /bin/tar --create --file /dev/null --directory /var > > --one-file-system --listed-incremental > > /var/lib/amanda/gnutar-lists/themoose.localdomain_var_0.new --sparse > > --ignore-failed-read --totals . > > runtar: pid 6507 finish time Wed Jun 21 08:24:02 2006 > > -------------------------------------------------- > > > > I notice that the file is /dev/null. Is that correct? > > > > During estimates is it. > > If gnutar outputs to /dev/null, it goes through all the > normal steps without actually reading the ordinary file > data blocks. Saves mucho time for estimates.
I checked all the runtar log files; they all indicate the same output file. Where do I look to see the results of a backup, if any? The amandad...debug files seem to be the right place, but the sizes are all way too small. -- Charles Curley /"\ ASCII Ribbon Campaign Looking for fine software \ / Respect for open standards and/or writing? X No HTML/RTF in email http://www.charlescurley.com / \ No M$ Word docs in email Key fingerprint = CE5C 6645 A45A 64E4 94C0 809C FFF6 4C48 4ECD DFDB
pgpGhNKD3WUai.pgp
Description: PGP signature
