This is apparently (I'm guessing) by design, but if so IMO it's broken by
design... :-\
In 7.2 --
1. Open tape library, pull a few tapes, close library and bring it back
online again.
2. Once the library completes its auto inventory (hardware-based,
triggered by bringing it back online), it ceases all activity.
3. Until "nsrjb -j <library> -I -S x" is run to inventory the now-empty
slots, Networker will go forever without knowing they're emtpy.
No problem.
In 7.5.1 --
1. Open tape library, pull a few tapes, close library and bring it back
online again.
2. Once the library completes its auto inventory (hardware-based,
triggered by bringing it back online), it ceases all activity. For a
moment...
3. Without any action from the operator, no nsrjb invocations, etc., the
library suddenly inventories itself again, possibly two or three times.
4. If "nsrjb -j <library>" is run, the slots in question ALREADY show as
being empty, without any further action from the command line. (??!!)
Problem.
This triggers "jukebox is not ready to accept commands" (or similar)
errors and causes aborted scripts under 7.5.1 that work just fine under
7.2. It now forces the operator to wait for some inderterminate period of
time until it's guessed that all activity on the library has ceased
(whereas before when it came back online all was OK). It appears
empirically that Networker is polling the hardware for on/offline changes,
etc. Seeing "Hardware status of jukebox '<library>' changed from 'detected
hardware change' to 'ready'" entries in the daemon.log seems to reinforce
this theory.
So, is there any way to disable or turn off this interference?
My general rule is: automatic <whatever> is OK as long as it can be
disabled upon demand. You know, "do what you're told and ONLY what you're
told" kind of thing... :-)
Thanks.
To sign off this list, send email to listserv AT listserv.temple DOT edu and
type "signoff networker" in the body of the email. Please write to
networker-request AT listserv.temple DOT edu if you have any problems with this
list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
|