* Benjamin Lewis <[EMAIL PROTECTED]> [20070914 09:09]: > Mark Scheufele wrote: > > [...]
In the snipped portion was a comment about how to cleanly zap an amanda run. I for one would love to have a 'amkill' sort of thing that would tell the clients to terminate cleanly and then wrap up all the amanda processes on the server without the need to amcleanup afterwards. just my 2¢, jf > > > But when I now run amstatus it still shows one DLE entry as dumping and > > the other ones as waiting for dump. > > > ***> Using /opt/amanda/etc/Weekly/log/amdump.1 from Thu Sep 13 19:00:01 BST > > 2007 > > > > nessie.diasemi.com:/cad 0 300187258k dumping to tape (21:43:28) > > nessie.diasemi.com:/design 1 2277k wait for dumping > > nessie.diasemi.com:/it 1 408683k wait for dumping > > nessie.diasemi.com:/projects 1 10453k wait for dumping > > nessie.diasemi.com:/users 1 121964k wait for dumping > > amstatus uses the most recent amdump logfile (amdump.1) if you haven't > specified a particular logfile (with the --file argument) and there isn't a > current logfile (amdump). There's nothing for you to do here; amstatus is > just showing you the status as of the time you killed it. A new amdump > logfile will be created during the next run of amdump and you'll be able to > see the new status then. > > -Ben > > > -- > Benjamin Lewis, CISSP <[EMAIL PROTECTED]> > Security Analyst, Identity and Access Management > IT Networks & Security > Purdue University -- <° ><
