According to Andrew Brown:
>
>yeah, the estimated finishing time is much more useful.
>

True, I was going to change it over and then just wondered, why not
have both... so that is what I did.  I have also made the timestamps
an option (you need to set the t flag) so that things that parse the
dump output will not get screwed up.  Here is a sample output:

bash-2.03# ./dump 0stf 100000 /dev/null /
  [11:56:14 GMT] DUMP: Found /dev/rwd0a on / in /etc/fstab
  [21:26:14 CST] DUMP: Date of this level 0 dump: Sun Aug 26 21:26:13
2001
  [21:26:14 CST] DUMP: Date of last level 0 dump: the epoch
  [21:26:14 CST] DUMP: Dumping /dev/rwd0a (/) to /dev/null
  [21:26:14 CST] DUMP: Label: none
  [21:26:14 CST] DUMP: mapping (Pass I) [regular files]
  [21:27:57 CST] DUMP: mapping (Pass II) [directories]
  [21:27:57 CST] DUMP: estimated 4773948 tape blocks on 0.59 tape(s).
  [21:27:57 CST] DUMP: Volume 1 started at: Sun Aug 26 21:27:57 2001
  [21:27:58 CST] DUMP: dumping (Pass III) [directories]
  [21:31:26 CST] DUMP: dumping (Pass IV) [regular files]
  [21:32:57 CST] DUMP: 2.99% done, finished in 2:42 (at 00:15:01 CST)
  [21:37:57 CST] DUMP: 12.01% done, finished in 1:13 (at 22:51:11 CST)
^C  [21:40:49 CST] DUMP: Interrupt received.
  DUMP: Do you want to abort dump?: ("yes" or "no") yes
  [21:40:51 CST] DUMP: The ENTIRE dump is aborted.

One thing that strikes me now is why is it necessary for me to mandate
the timestamp format at all?  I should just have an environment
variable that you can set the strftime format in and that will be used
for the logging (default it to "%T %Z" or whatever) - using an env
variable gives the user control over the log output which would be
nice IMHO.

-- 
===============================================================================
Brett Lymn, Computer Systems Administrator, BAE SYSTEMS
===============================================================================