-oneunit flag on 5.04 Stanford Service Install

[harlam357]

I think this is gonna be a ChasR question or answer... however you wanna look at it. Just like to get some feedback if anyone has any experience using the -oneunit flag on a Stanford service install (ImagePath key)

The reason for asking is b/c it has yet to work for me. I can set -oneunit in the ImagePath and the console sees the flag... heck even after that WU the log file shows the core/console as being stopped (no further logging). BUT... the console proceeds to download another WU and begin working on it, just as if I had not specified the -oneunit flag (but no logging- at least not the main log file).

So what's the scoop? Has anyone else experienced this behavior? Again, this is on 5.04. Haven't tried 5.02 Stanford service install (all my others are Wedo style).

The only thing I haven't tried or that I may have borked is that I've rewritten the ImagePath key as a REG_SZ (standard string) and not a REG_EXPANDED_SZ (expanded string). But the other flags are being read correctly, so I'm not apt to blame the string type. After all, there are no expandable variables in the ImagePath, so the length should stay static upon evaluation.

:confused: :shrug: :confused:

['Cuda340]

I've tried using that flag a couple times myself with the same results as you Harlam. :confused:

[TalRW]

I have used it and gotten it to work. The thing is you can not reboot if you reboot it will DL another workunit but if not it will stop. I put it in the image path line in regedit.

[7im]

The service is just doing what it is supposed to do. Check the properties of that service. It is probably set to restart the service if the application ends (shuts down after oneunit) The service just starts up fah again, and keeps crunching. The oneunit flag is kinda contrary to the concept of running the client as a service anyway.

What is the point of using the oneunit flag with a service? Maybe we can figure out a better way to do what you want it to. For instance, and scheduled task might work better.

[ihrsetrdr]

I used to do service installs but now-a-days like to have more/easier control over the client and start with a desktop shortcut and minimize the console. I find that when overclocking or dealing with problems It's handy not-to have the client trying to always start upon reboot.

[harlam357]

@cuda- glad I'm not the only one.

@TalRW- no reboots... most of my rigs haven't been rebooted in weeks. Are you sure you're running 5.04 & not 5.02?

@7im- No it's not doing what it's supposed to do. ;) And contrary or not, it should work. And when doing so on a 5.02 Wedo install it works flawlessly. However, as you elude, the flag does not actually put the service in a "Stopped" state. The console itself has no ability to actually manipulate the service directly, it takes user intervention. If you look in "services.msc" you will see that the service is still in a "Started" state after using the -oneunit flag. But the actual console has stopped and the core disengaged. Making the only way to restart the console is to manually stop the service and restart it. Again, user intervention. By default all the recovery options on the service are set to "Take No Action". So that isn't it either.

@IH- I agree... but the way I handle it is, after install, set the service to Manual and not Automatic. That way it won't start until you tell it to. :) Shucks... I was gonna have you beta my client service manager. I need someone to test a quad install. Your 2x2 Opty immediately came to mind. ;) But my manager only works with service installs. :(

Thanks for the help all... my reason for asking is because I'm trying to put the finishing touches on this (http://img.photobucket.com/albums/v663/harlam357/screen%20shots/FAH/FAHControl2.jpg).

[silent bob]

thats looks nice . you would be able to change stuff "on the fly?" or still require a restart of Fah , either way looks like alot of time went into that
keep up the good work

[ChasR]

The service must be set to manual when you add the -oneunit flag in the registry. If you don't do that, Windows, the all knowing OS, will restart the service. It works everytime when the service is set manual.

Edit: WRONG, the service restarts and FAH downloads a new WU even if set to manual

[harlam357]

@silent bob- Thanks! :beer: It's been fun... and I'm getting close to a release beta. To answer your question... no, you'll still need to stop and restart the client for changes to take effect. But it'll do that for ya. ;) Also, the coolest option, IMO, is being able to "talk" to other instances of the program running on other machines on your network. I can start/stop, set options, view logs on other machines all from my main machine. A lot better than VNCing into other machines or likewise physically going to that machine and setting options "the old fashioned way". :)

@ChasR- all my clients are set to Manual (should've mentioned that before). I think it might be due to the ImagePath key not being set to a REG_EXPANDED_SZ anymore. Will also try a 5.02 Stanford install and see if it works as well. Will report back.

[||Console||]

@cuda- glad I'm not the only one.

@TalRW- no reboots... most of my rigs haven't been rebooted in weeks. Are you sure you're running 5.04 & not 5.02?

@7im- No it's not doing what it's supposed to do. ;) And contrary or not, it should work. And when doing so on a 5.02 Wedo install it works flawlessly. However, as you elude, the flag does not actually put the service in a "Stopped" state. The console itself has no ability to actually manipulate the service directly, it takes user intervention. If you look in "services.msc" you will see that the service is still in a "Started" state after using the -oneunit flag. But the actual console has stopped and the core disengaged. Making the only way to restart the console is to manually stop the service and restart it. Again, user intervention. By default all the recovery options on the service are set to "Take No Action". So that isn't it either.

@IH- I agree... but the way I handle it is, after install, set the service to Manual and not Automatic. That way it won't start until you tell it to. :) Shucks... I was gonna have you beta my client service manager. I need someone to test a quad install. Your 2x2 Opty immediately came to mind. ;) But my manager only works with service installs. :(

Thanks for the help all... my reason for asking is because I'm trying to put the finishing touches on this (http://img.photobucket.com/albums/v663/harlam357/screen%20shots/FAH/FAHControl2.jpg).I have a dual xeon with ht so quad fah if you need some one to test it

[harlam357]

As long as you're running a quad service install you're on the pre-beta list. :D

Thanks Console! :beer:

[7im]

Wedo probably used srvany.exe to create his service installer? It's probably a lot like the installer that I use, here: http://devel.bluetentacle.co.uk/dc/fahservice/index.htm

The above installer is more customizable. I don't know what Stanford uses for their native service installer, but switches aren't really supported by the Stanford service install. Maybe in the next version of the client.

[ChasR]

7im has hit on something here. I went looking at 5.04 beta and oneunit because I'd had a few run on, but in both cases I had forgotten to set the service to manual. Stanford uses -svcstart where Wedo used -srvany. Flags have to go in image path on the service started with -svcstart whereas they go in parameters\AppParameters with the -srvany started service.
From experience the forceasm flag works in imagepath.
I'll do a little testing. It could be my aging memory is playing tricks on me and it has never worked.

[ChasR]

I set one to service as manual and -oneunit as the last flag under ImagePath. Now I have to wait 15 hours for it to finish.
In the meantime, while I test my memory, with the services are set to manual, you can always stop them and and run FAH504-Console.exe from the command line with the -oneunit flag and whatever other flags you want.

[ChasR]

THe one unit flag simply does not work when added to the ImagePath key of the registry on a 5.04 service install. Work around is to stop the service, set it to manual or disable and launch FAH with the run command adding the -oneunit flag.

[harlam357]

Well... that's not what I was hoping to hear. But it is what I expected to hear.

Now I just need to disable adding the -oneunit flag on my control when interfacing with a Stanford Service install. Not a problem. ;)

Thanks for the confirmation ChasR! :thup:

[TalRW]

@TalRW- no reboots... most of my rigs haven't been rebooted in weeks. Are you sure you're running 5.04 & not 5.02?


Oh yes I just checked I'm using 5.02. Just keep in mind you are using a beta version all the features might not work perfectly.