Hi, Rohit,

on Mittwoch, 04. Februar 2004 at 15:41 you wrote to amanda-users:

>> Run
>> 
>> amflush -fs DailySet1
>> 
>> so you get the messages to stdout.
>> Gives a load of info ...

R> $amflush -fs DailySet1
R> /usr/sbin/amflush: invalid option -- s

Hmmm. I don't exactly know when this option came into game.

As Paul assumed in another branch of this thread, you might have more
than one AMANDA-installation on your machine.

Have you tried several installations and maybe failed to remove one?

What does a simple "find / -name amflush -type f" give you?

If you find more than one amflush, it is very likely that you call
"the wrong one". Maybe it was compiled with different directories and
such.

Verify that you have ONE binary. If more, verify the execution of each
of them. If you find out that one works, get rid of the others. In
case of several mixed-up installs I would take the effort and
recompile a clean and fresh 2.4.4p2 after removing the old
AMANDA-binaries.

--

Also verify what Jon and Paul assumed:

Check if the directories contain something useful or if the contain
something that does not belong there. What is the "windows"-dir there?

In a properly configured holdingdisk there should not exist anything
else than files created by amdump.

"There shall not be anything beside me!", if you like it that way ;)

Also check permissions and stuff.

If the s-option of amflush does not work, check your amanda-logdir for
files like amflush.log (I assume it would be called like that as I
currently have no access to my testbox). This file should contain
useful information about what happens and how far the flush gets.

--

best regards,
Stefan

Stefan G. Weichinger
mailto:monitor AT oops.co DOT at