>Date: Tue, 12 Dec 2000 19:49:11 -0800
>From: Jeff Silverman <[EMAIL PROTECTED]>
>Hi. My /usr file system overflowed and so amanda was unable to write to
>/usr/local/etc/amanda/changer*. Technically, that's a bug in amcheck
>(it ought to detect if those files are writable) but skip that for now.
>What I really want to know is what is in those files? I think that
>changer-slot is the current slot number. changer-clean might be the
>slot with the cleaning tape in it. But what is changer-access? If it
>is empty, what does that mean?
The files are used by your changer program (or script), if at all.
There exist a variety of such programs (scripts); some are supplied with
amanda; some are cobbled up at a given installation.
But since I can't tell what changer program you use (from the above --
well, I suppose I could look at all of the changer programs supplied
with amanda and figure out which ones reference the files you named, and
assume that you're using an amanda-supplied one...), I can't tell you
the answer to your question.
I suspect that you're correct about changer-slot, though someone could
have been Very Perverse in writing a changer script....
And as for amcheck, it can tell the name of the changer program (if any)
you specify that you want to use, but it cannot tell what (if any)
auxiliary files that program might use or how it intends to use them.
(Maybe the changer script API should be slightly modified to accept a
"check" parameter; if that is specified, the script could do its own
reality-check routine, whine as appropriate, and return !0 if something
appears wrong. And if the changer can't cope with "check", it should
just return some defined value -- either 0 for backwards-compatibility
or (say) 1 for "I haven't a clue what you're talking about". Then
amcheck could invoke the changer with the "check" parameter....)
Cheers,
david
--
David Wolfskill [EMAIL PROTECTED] UNIX System Administrator
Desk: 650/577-7158 TIE: 8/499-7158 Cell: 650/759-0823
