Networker

Re: [Networker] stopping savegroup

2005-08-04 05:42:10
Subject: Re: [Networker] stopping savegroup
From: "King, David - Eastman" <dking AT EASTMAN DOT COM>
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Date: Thu, 4 Aug 2005 05:33:53 -0400
I've not used nsradmin.  Do you have a code snippit or such?
 
I would love to use nsradmin to start the groups, and I've been looking
for a way to tell if the group is finished!
 
I'll look at pskill.  Would it stop the savegroup?
 

David L. King 



________________________________

From: Dave Gold - News [mailto:dave2 AT cambridgecomputer DOT com] 
Sent: Wednesday, August 03, 2005 10:18 PM
To: networker AT listserv.temple DOT edu
Cc: King, David - Eastman
Subject: stopping savegroup


David,
 
If you are starting savegrp directly, you should be able to kill the
process (sysinternals has, in my opinion, the best kill command--look
for pskill) ...however, have you considered starting the group via
nsradmin instead of starting savegrp? Then you can stop the group via
the GUI, or via a nsradmin command, which should make it a bit easier.
 
If you need to know when it finishes, you could have the perl script
then run nsradmin every few minutes and check to see if that group was
still running. (I wasn't sure if the perl and cmd process were still
running because you cared when the savegrp ends or not)
 
Another advantage is that nsrim will run automatically afterwards.
 
Dave
 
Date:    Tue, 2 Aug 2005 18:28:12 -0400
From:    "King, David - Eastman" <dking AT EASTMAN DOT COM>
Subject: Halting a savegroup started by a remote scheduler


We use a third party scheduler that logs onto our Legato servers
worldwide (all W2K3 with NW 7.1.3 or 7.2) using an administrative
account and runs a PERL script that does a savegrp command.  Along with
the usual processes (savegrp, nsrmmd, etc) are a cmd and perl process.

The problem is that we cannot halt the savegroup without recycling the
Networker services.   Since we have other backups and clone jobs
running, we do not wish to do this.

I tried killing the savegrp, cmd and eventually all processes for that
account, but the savegroup didn't stop.   If only one client is still
running, I can kill the save process on that client, but otherwise
cannot stop the savegroup.

Any ideas?


David King


[* Internet Mail *]


--
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
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=

<Prev in Thread] Current Thread [Next in Thread>