Quote:
Originally posted by Joe
Umm why?? why is it that much work?
why not just AT them (schedule them) to run at different times.
all I do is click a bat file and it sets up the start up and shut down time for the folding on every machine I want. I have another bat file to push out all the folders and files, and I have a few failsafe bat files to cancel all the jobs on all the machines, and remove all traces of the folding.
Edit: I made a thread about this here : http://forums.procooling.com/vbb/sho...&threadid=7863
|
It's a nice little set of jobs there Joe - but my environment is a little bit more complicated. It sounds like you're using mostly single-processor workstations to fold at night, while I'm using multi-processor servers. I could cut'n'paste the batch files to double-up everything and run two instances of the service on each machine - but that doesn't help if i want to push it to a quad-processor or two, and I don't think that the service-mode supports more than two instances. Also - using scheduled jobs and services are just two more things that have a possibility of leaving entries in the log files if something wierd does happen.
My current method has shortcuts on the desktop (in my profile only) one for each processor/instance and I remote-desktop to the server (these are all Win2K Server so this gives me a virtual terminal, not the local console), click my shortcuts, and then close the terminal window without logging off. The batch-files I've got of the desktop are set to kill the folding client after 12 hours - so I start them between 5:00 and 6:00 AM (I work later than everyone else - most leave at 4:30), and they shut themselves off early next morning before people arrive (which is good because I start later than everyone else - flex-time is good) I'm spending my free time here investigating a way I can run a single file from my workstation to start all of the clients and the 12-hour timer than kills them, but still have them running as a standard process instead of a service on each server. And for weekends I just have a second copy of the batch file with a 60-hour timer instead. I didn't get to run it last weekend though because I took Friday off to go camping early.