Hi, Paul Bijnens,

on Montag, 09. Februar 2004 at 13:56 you wrote to amanda-users:

PB> Rohit wrote:


>>>And, more generally: Should amcheck complain about that?
>> 
>> Yes, I think it should with appropriate message. 

PB> If you don't put cruft in the amanda holdingdisk directory,
PB> then there is no problem.   (It did complain about the cruft,
PB> didn't it?)

It stalled because of the permissions on the cruft.
And it complained about the cruft, not the permissions, which is fine.

Looking at it from the improve-the-docs-angle I suggest adding some
lines to the docs/INSTALL-file (which seems to be a common start-point
for new AMANDA-users) that recommend to do the following:

- create a unique dir for each config's holdingdisk, so that the
files for multiple configs don't get mixed up.

e.g.

<some-fs-to-use>/amanda_hold/<conf1>
<some-fs-to-use>/amanda_hold/<conf2>

- give the holdingdisk to the AMANDA-user

- chown -R <amandauser> <some-fs-to-use>/amanda_hold
- chgrp -R <amandagroup> <some-fs-to-use>/amanda_hold
- chmod -R 660 <some-fs-to-use>/amanda_hold

(or any other permission you like/need/want, just make sure
<amandauser> has r/w-access).

- leave the holdingdisk to AMANDA alone. Nothing else should go in
there. If AMANDA complains about cruft, go and have a look. (Re)move it.
Cruft can lead to strange behavior of amflush, for example.

--

The docs/INSTALL-file does not contain any tips on creating
holdingdisks. Maybe it should.

-- 
best regards,
Stefan

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