• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Dnet shutdown command

B

bthom70

Junior Member
New memeber here, from the land of Sysopt.
But I have a question regarding shutting down a client from a shared folder on NT4.
I read, heard somewhere that the exitrc5now file added to the folder should shut the clients down, but is doesnt.
Does anyone else have any ideas??


bthom70
 
HMM, I've never heard of the exitrc5now thingy, but dnetc.exe -shutdown works fine in Linux and Win95/98/Me. Don't know about NT, though.

Russ, NCNE
 
I know about the command line shutdown.
But it doesnt shutdown all of the clients running in the building (BIG BUILDING)
And I can not spare the time to manually go to each machine to shut the client down or have the users log off.

Any other suggestions?

bthom70
 
A. I need a way to shutthem down when we run some crazy software here.
B. I want to move the shared folder.

edit, Mech Im not switching teams, Im only here to ask for help perhaps post if I can to help you guys out at a later date.
Im running rc5 on mishmash of cpus and at various daily usages.
ranging from p133-pIII800
99% are OEM Compaq or IBM so no overclocking here.

bthom70
 
From the configuration menu in the client:

distributed.net client configuration: General Client Options
--------------------------------------------------------------------------

Exit flagfile Path/Name:

While running, the client will occasionally look for the the presence of
this file. If it exists, the client will immediately exit and will not
start as long as the file continues to exist.

Default Setting:
Current Setting: exitrc5.now
New Setting --> exitrc5.now

Perhaps if you had the client run from a shared folder on a machine that is always on, you could simply use this feature, but that route has some obvious pitfalls. Why do you need to shut the client down, anyway? Could you perhaps use the "Work for x hours, then exit" feature to accomplish your goal, or run the client as a service so it is out of the way?

Edit: or perhaps you can write a batch file that will accomplish this on all the machines at once in their respective dnet folders.
 


<< I need a way to shutthem down when we run some crazy software here. >>

You can use the &quot;pause while program x is running feature&quot;
Unfortunately, I don't have the details at hand, but you can specify a list of programs that will cause DNETC to automatically pause. Perhaps someone else can help out with the details.
 
the client is the lowest priority process running. Anything that needs the cpu will most definitely take it from the dnetc client.
 
joe O has a good point. It can pause when a certain app is running and then start up again when it is finished
 
<< I need a way to shutthem down when we run some crazy software here. >>
Short version, the major software we use has a lot of bugs in it, healthcare stuff. The software vendor likes to look at whats running when bugs pop up.. www.sysinternals make filemon.
To recreate problems I prefer to have a system wide method to kill all clients. We use filemon to see EVERY file in use and requested.
All of our clients are 9x or 2k(laptops only) server is NT4.
I have the clients run from the login script and would like to have better control of them without an intricate remtoe cows or install on each and every machine.
I understand about the cpu usage stuff but having less to point fingers at is a great timesaver, when the see something else thats the first thing they blame.
Plus having 1 common sharefolder ir better for me, I know sooner or later I'll have to invest time in remote cows or something, but it works for now.
 
Welcome to our SysOpt RC5 brethren.

Yes, this is an interesting problem that you have brought to the table..

Remote cows takes care of the NT machines, but that is of little help in this situation.🙁

Best of luck, and a free bump^

viz
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top