PRP and SOB Service Question

[Stromkarl]

Hello everyone,
I have a strange request. In the settings window for the SOB client, there is a check box to finish the test and NOT request another block. Why does the SOB Service force the client to get another block with this check box filled in? I have the current client and service and it is installed on a Win XP box. I have turned on both the options on to restart stalled clients.

If this is something that could be added to the service, I would greatly appreciate it. I have a couple of boxes that I cannot PRP on any more and would like to transfer to another computer.

Thanks,
Stromkarl

[Stromkarl]

I guess this would be for Mathguy only, since he wrote the service. Has anyone heard from him lately? Or is he MIA?

Stromkarl

[Vato]

You can alter this behaviour by use of sobsvc -m (see the ReadmeNT file).
Possibly -s as well.

You may also need to make sure you don't have the service set to restart automatically by windows.

[cjohnsto]

Just to explain: you probably have the service set to restart stalled clients. When it stops work (due to the option you checked) the service restarts the program which causes it to fetch more work.

[Stromkarl]

Thank you guys. I appreciate the help. :thumbs:

I have read the ReadmeNT.txt file many times over the years I have been using it. I am the first to admit that there are a few things in the documentation that I still don't understand. :confused: However, the -m and -s switches are not on that short list. :D
My problem is that a stalled client and a client set to end after the current block are two different things, IMO. :umm: When the option to stop after the current block finished was added to the client, the service wasn't updated to check this setting and override the -m and -s switches. :help: I figured I would have to shut off the -s switch to fix this, but it seems cumbersome and a bit frustrating. :bang:

Thanks again,
Stromkarl

[MathGuy]

Yeah, I was wondering when somebody would finally get around to noticing this...interestingly enough (or maybe not) the "finish after current block" client option was added at my request, since I wanted to have a clean way of reducing the number of client instances in the service handler without having to manually expire a block.

Well, Louie did his part but I never did mine...I'm headed down to the Gulf next week to do some Katrina cleanup, and I expect to be behind in all sorts of RL stuff when I get back from that. BUT I will try to devote a few cycles to the service handler and hopefully knock a few items off my SOB to-do list (this one included).

--MathGuy