> >I'm creating an script to stop our networker server. This script will be
> >integrated in our automatic shutdown system of machine in case of emergency.
> 
> You didn't indicate which version of NetWorker you are using and 
> which OS your NetWorker server runs on. Also, may I ask why you
> are doing this? If on a Unix platform, why not just use "nsr_shutdown"
> and leave it at that?

Agreed.  I'd really want to know what advantages a more complex script
to eject stuff would have over just shutting down.

However, here are some ideas:

#1 Use nsradmin to set 'stop now' to 'true' for running groups.  This
   will stop an autostarted group.

#2 Kill 'nsrexec' processes.  This will abort most jobs invoked by the
   server.  

Neither will do anything about a client running a 'save' manually, which
is talking directly to nsrd/nsrmmd.

If you're not worried about having to possibly re-inventory later, you
could shut down networker.  Then when the tapes were released, 'mt' to
eject all the tapes.  Then use sjimm to have the robot move the tapes
back into the slots.  It's a little more "brute force", but will
probably work in one or two scenarios that just asking Networker to do
it nicely might not.

-- 
Darren Dunham                                           ddunham AT taos DOT com
Senior Technical Consultant         TAOS            http://www.taos.com/
Got some Dr Pepper?                           San Francisco, CA bay area
         < This line left intentionally blank to confuse you. >

--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listserv.temple DOT edu or visit the list's Web site at
http://listserv.temple.edu/archives/networker.html where you can
also view and post messages to the list. Questions regarding this list
should be sent to stan AT temple DOT edu
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=