2 Intern

 • 

724 Posts

August 20th, 2008 14:00

Only way I've found to do this is stopping Nw services at the client. It's not a good solution, but works :)

1 Rookie

 • 

58 Posts

August 20th, 2008 14:00

Yes, I did that as well but there got to be a better way (through command line??)

2 Intern

 • 

724 Posts

August 20th, 2008 14:00

If there's one, it's very well hidden! As long as I work with Nw, I've always told my customers that if they have a group with a large number of clients, they can have this situation where they cannot stop only one client (except if they force the error stoping the client services).

I usually put large clients into a dedicated group for each one due to this "problem", so if I need to stop one client, I abort the related group.

29 Posts

August 25th, 2008 08:00

The best way is to stop services on the client as it was already pointed out, there is no other way,

regards
Abdon

4 Operator

 • 

14.4K Posts

September 4th, 2008 07:00

Well, killing service or save process is the only way. I wish for years engineering would implement job control where I could select job and stop it or even do pause, but this is still on wish list. I was hoping to see that when nsrjobd was introduces, but it was not there. Nevertheless, it could first step towards my wish to become true.
No Events found!

Top