Err... -oneunit flag

SiriusB

SiriusB

SiriusB

Soldato
Joined
16 Dec 2005
Posts
14,443
Location
Manchester
Does the -oneunit flag only work the next time it starts a new WU? I added the -oneunit flag to my client last night, and when I check it today it had started a new WU...

Was hoping to install my Q6600 today, but I can't find my AS5! :(
 
It normally works on the current WU too.

Was this the SMP client? Some of the flags tend to work unpredictably with it, especially the Windows one.

(edit) And is it a service installation? Using -oneunit on a service confuses it too.
 
Linux SMP client [native]

I'll see what it does with this WU later on. If it fails again I'll just nuke it. Not the best action but I'm not waiting another day for a WU to finish.
 
Was it running at the command line or was it running as a service (as finstall would have it)?

Why stop work anyway? If you're working now Linux won't be bothered by having a different processor installed. You won't even have to do anything with it since you're already running an SMP kernel. turn it off, yank the old processor, install the new one, and reboot. It won't miss a beat.
 
What would we do without you billy :D

If you can wait two days I'll post you some AS5 (it's at home atm) but someone local might me able to pop round quicker (have you tried MM)
 
My AS5 isn't that lost! Thanks for the offer though. I could have searched harder but I had other things to do today.

I know Linux doesnt much care about what you do to the hardware, but I assumed the client may take offence. I wanted to have the client finish a unit and stay switched off to avoid losing a WU.
 
Assuming it starts automatically, you could temporarily stop it starting when the PC starts? Cange the processor, overclock the pants off it, run some stress testing then start the client again. No danger to your WU as it should be stable when you evetually turn it back on again.

Though obviously it would be a tight time frame to overclock and stress test during an SMP WU.

Theres a challenge for you :D
 
I don't think the client will care TBH! It's hard-coded always to run four core processes anyway, so each one will just be allocated to a core. I'm not sure the cores are aware of how many CPUs are available - probably managed by the OS.
 
I think you should all stop talking about your bottoms before Slackworth comes along and distributes spanky justice to you all!
 
OK, if -oneunit is broken, here's the easiest way to stop the client connecting :-

Stop the client, run -configonly and set proxy to 127.0.0.1 and some random port. Restart the client and let it run.

When it's done, it'll try to connect and fail. Stop the client, run -configonly to reset the proxy and then -send all to send the result. Job done.
 
Biffa said:
I think you should all stop talking about your bottoms before Slackworth comes along and distributes spanky justice to you all!
Click to expand...

:p

If my client doesn't stop after this WU I'll just stop the client and risk it.

I have most of tomorrow free so will have a shuftie for my AS5. I can always go direct to a certain online retailer and pick some up. I want this quaddie up and running by the end of the day :D

Probably wont be overclocking it until I have seen what its temps are like. My Ninja is struggling with my E6600, so I doubt I'd get a big OC with it on a quad.
 
Well it never hurts to let a WU complete before restarting/changing anything - if it's gonna throw a fit it's more likely to be with a mostly completed WU than with a fresh one :p :o
 
I've copied a complete WinSMP folder from a C2D PC to a C2Q and the WU carried on running without any problems at all (but almost three times faster...).
 
You must log in or register to reply here.
Back
Top Bottom