Max Waterman wrote:
Phil Homewood wrote: | amdump doesn't generally (ever?) give output on stdout -- it | emails it.
You can generate the email by hand and safe it in a file instead:
cd ~amanda/DailySet1 amreport DailySet1 -l log.XXXXX.X -f save-mail-file
At least if you have file named log.datestamp.lvl. There should also be a file named amdump.1 with a detailed log of the serverside amdump program. Any useful error message in that file?
# su amanda -c "/usr/sbin/amadmin DailySet1 info"
Current info for localhost /home: ~ Stats: dump rates (kps), Full: -1.0, -1.0, -1.0 ~ Incremental: -1.0, -1.0, -1.0 ~ compressed size, Full: -100.0%,-100.0%,-100.0% ~ Incremental: -100.0%,-100.0%,-100.0% ~ Dumps: lev datestmp tape file origK compK secs
Make any sense?
Seems to me like amdump did nothing at all.
-- Paul Bijnens, Xplanation Tel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUM Fax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *********************************************************************** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, * * quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... * * ... "Are you sure?" ... YES ... Phew ... I'm out * ***********************************************************************
