Joel Fisher wrote:

> I've got a resolution for #5, with the empty slots and allocating
> volumes not physically in the silo.  It appears in all the
> troubleshooting and what not over the last week, that some volumes got
> removed from the silo without networker knowing about it.  You used to
> be able to clean this up by just nsrjb -x -T <volser>.  Now, with the
> new nsrlcpd process, it holds its own view of what is in the silo, and
> if volume removal doesn't happen in the right sequence nsrlcpd gets out
> of sync with acsls/libstation.  End of the day, I just needed to
> disable/enable the silo in NMC and that stops and restarts the nsrlcpd
> process which causes it to get fresh info from acsls/libstation.  This
> resolution didn't cause any disruption to my environment.
> 

Interesting to note that the behaviour of nsrlcpd has changed at 7.4.3.
It now locks the jukebox port, meaning that you cannot see the robotics
with inquire, or with any of the low level commands when nsrlcpd is
running. If you need to run sjirdtag or similar you would need to
disable the library first, and remember to re-enable it afterwards.

I guess a lot of people's scripts are going to break...

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