Now I'm more confused. :)
The docs for mtx-1.2.10 say to use CHANGER, while the older versions
seemed to use TAPE. I assume that's why the chg-zd-mtx was written
with the $TAPE variable. 1.2.10 also will honor TAPE or CHANGER, which was
why I had never changed it before.
If if it doesn't matter if it's called TAPE or CHANGER, I'd like to have
it as CHANGER, since that what their docs now suggest.
Thoughts?
On Fri, 02 Mar 2001, Joe Rhett wrote:
> Sorry - wrong maintainer. The problem isn't chg-zd-mtx, it's the 'mtx'
> program itself which uses the $TAPE environment variable. Sorry for the
> confusion.
>
> On Fri, Mar 02, 2001 at 09:22:44AM -0500, Jason Hollinden wrote:
> > Here is a patch for the current CVS version of chg-zd-mtx.sh.in that
> > changes the $TAPE variable to $CHANGER. It was only used 3 times, so it
> > was pretty painless.
> >
> > On Thu, 01 Mar 2001, Joe Rhett wrote:
> >
> > > As others have said, it uses the TAPE environment variable. I wish we could
> > > convince the maintainer to use CHANGER instead, so it doesn't conflict with
> > > mt's TAPE environment variable <sigh>
> > >
> > > Anyway, make sure you are using either the version we made
> > > http://www.noc.isite.net/?Projects
> > >
> > > or the version someone else did which supports barcodes. The version
> > > distributed with Amanda doesn't work with modern versions of mtx and has
> > > numerous bugs.
> > >
> > > On Wed, Feb 28, 2001 at 01:24:12PM -0500, Stan Brown wrote:
> > > > I'm trying to get my first tape changer working, and I'm a little confused.
> > > >
> > > > It appears that I need to use the chg-zd-mtx scriptm but the version of mtx
> > > > that I have is used like this:
> > > >
> > > > mtx -f /dev/sg0 next
> > > >
> > > > for instance. Now it appears to me that chg-zd-mtx just runs mtx like this:
> > > >
> > > > mtx next
> > > >
> > > > That is wihtout the device specifier. Now it is possible for my version of
> > > > mtx to use the CHANGER environment variable, instead of the -f argument,
> > > > but I can't see anywhere that gets set in chg-zd-mtx either, and since this
> > > > will ultimatley be run fron cron, and thus potentialy be somewhat
> > > > "environmently chalenged", I am wondering how this is usually handled?
> > > >
> > > >
> > > > --
> > > > Stan Brown [EMAIL PROTECTED] 843-745-3154
> > > > Charleston SC.
> > > > --
> > > > Windows 98: n.
> > > > useless extension to a minor patch release for 32-bit extensions and
> > > > a graphical shell for a 16-bit patch to an 8-bit operating system
> > > > originally coded for a 4-bit microprocessor, written by a 2-bit
> > > > company that can't stand for 1 bit of competition.
> > > > -
> > > > (c) 2000 Stan Brown. Redistribution via the Microsoft Network is prohibited.
> > >
> > > --
> > > Joe Rhett Chief Technology Officer
> > > [EMAIL PROTECTED] ISite Services, Inc.
> > >
> > > PGP keys and contact information: http://www.noc.isite.net/Staff/
> >
> >
> > --
> > Jason Hollinden
> >
> > SMG Systems Admin
>
> > --- chg-zd-mtx.sh.in.20010302 Fri Mar 2 08:57:17 2001
> > +++ chg-zd-mtx.sh.in Fri Mar 2 09:00:39 2001
> > @@ -88,8 +88,8 @@
> >
> > myname=$0
> > tape=`amgetconf$SUF tapedev`
> > -TAPE=`amgetconf$SUF changerdev`; export TAPE # for mtx command
> > -if [ "$tape" = "/dev/null" -o "$TAPE" = "/dev/null" ]; then
> > +CHANGER=`amgetconf$SUF changerdev`; export CHANGER # for mtx command
> > +if [ "$tape" = "/dev/null" -o "$CHANGER" = "/dev/null" ]; then
> > echo "Both tapedev and changerdev must be specified in config file";
> > exit 2;
> > fi
>
>
> --
> Joe Rhett Chief Technology Officer
> [EMAIL PROTECTED] ISite Services, Inc.
>
> PGP keys and contact information: http://www.noc.isite.net/Staff/
--
Jason Hollinden
SMG Systems Admin
