That's what I did to make me believe something was a miss and post to the list.
Thanks,
James
Christoph Scheeder lt;[EMAIL PROTECTED]gt; wrote:
Hi,
there is a verry easy way to tell what amflush is doing:
amstatus configname
it shows you which dump is actualy getting flushed, which are
Just to update this. I tried it again (choosing a different directory and in the
foreground). This is the current ps -ef |grep amanda:
amanda 30890 30809 76 17:13 pts/000:02:23 amflush -f normal
amanda 30891 30890 0 17:13 pts/000:00:00 driver normal nodump
amanda 30892 30891 0
Hello Everyone,
I've recently deployed amanda. The client forgot tapes on several occasions and
I've got 4 backups in my holding area. I initiated the amflush command and
followed the instructions. The job kicked off in the background and I've been
using:
ps -ef |grep amanda
to see if the
James Marcinek wrote:
I've recently deployed amanda. The client forgot tapes on several occasions
and
I've got 4 backups in my holding area. I initiated the amflush command and
followed the instructions. The job kicked off in the background and I've been
using:
ps -ef |grep amanda
to see if the
I initially just straced the parent process (22802 amflush normal) which didn't
output anything:
Here's the ps -ef again with the trace commands for each PID involved:
ps -ef |grep amanda
amanda 22803 22802 0 14:01 ?00:00:00 driver normal nodump
amanda 22804 22803 0 14:01 ?
