>I got it. Thanks a lot. I'll install it first thing tomorrow morning.
Let me know how it goes. In theory :-), it's perfect. But I don't
run mtx here so debugging has been a bit of an adventure. It's ever so
faintly possible there is a miniscule portion of a tiny chance you'll
find a problem. But if so, send me the output of what you tried, the
corresponding /tmp/amanda/*debug file, and why you think it's wrong
(in case it's not obvious).
>> Even in the old script there is a block of comments about the format
>> of the config file. Just make sure you throw away all the lines you
>> don't need (it doesn't handle comments) and put keyword=value entries
>> in exactly like it says (the new version tries to be a bit more tolerant).
>
>I'm sorry I'm a bit confused here. Do I need to remove all unnecessary lines
>from the chg-zd-mtx.sh file or from the mtx-changer.conf file?
What I meant was, if you're going to use the old script:
* take that section of comments that describe the config file
* put them into your config file and uncomment each line, also
removing all leading whitespace
* remove anything faintly resembling a comment from the config file
(e.g. the extra stuff at the end of the lines)
* remove any lines that do not apply (e.g. if you don't have a
cleaning cartridge) and change whatever other values as needed
* Make sure all the settings are keyword=value, with keyword at the
very start of the line (no leading whitespace), no whitespace around
the equals sign, and no whitespace after the value.
This will also work fine with the new script, it's just that it tries
to be more tolerant of the comments, whitespace, etc.
The real problem was that the old script didn't pay attention to
comments, so if it saw something like this:
# This is not real: keyword=value
It would set keyword to value even though that's not what the installer
had in mind. And when the installer just copied the comments from
the script to the file, without removing the stuff that was not needed,
madness ensued as variables got unexpected values.
>Greg
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
