Message boards : Web interfaces : Do work while computer is in use?
Message board moderation
Author | Message |
---|---|
Send message Joined: 30 Aug 06 Posts: 13 |
Hi BOINC folks, I have a server that I share with some other folks here at work. I put BOINC on it (with permission), but I told them I could set it to not do work while they were on the machine. What we've noticed is that setting only works while I am logged in - when they are logged in it continues to crunch. Did I do something wrong or is that setting profile specific in Windows? Thanks, -ST |
Send message Joined: 29 Aug 05 Posts: 15560 |
How did you install it? As a service? |
Send message Joined: 30 Aug 06 Posts: 13 |
How did you install it? As a service? No, will that work if I did that? |
Send message Joined: 29 Aug 05 Posts: 15560 |
If you install it as a service, it'll work in the background for whomever logs on to that computer. They shouldn't even notice it. Make sure you don't let Boinc (Manager) start up at logon though. Isn't needed either, just keep a shortcut available for your own logon. |
Send message Joined: 30 Aug 06 Posts: 13 |
If you install it as a service, it'll work in the background for whomever logs on to that computer. They shouldn't even notice it. Make sure you don't let Boinc (Manager) start up at logon though. Isn't needed either, just keep a shortcut available for your own logon. Thanks Jord, I'll try that today. |
Send message Joined: 30 Aug 06 Posts: 13 |
If you install it as a service, it'll work in the background for whomever logs on to that computer. They shouldn't even notice it. Make sure you don't let Boinc (Manager) start up at logon though. Isn't needed either, just keep a shortcut available for your own logon. Darn. No dice. It continues to run while you are logged in, despite setting it not to do that in the project prefs. I think this is going to prevent me from deploying this more widely until I can get that setting to be profile independent in Windoze. Thanks for the help Jord. Any other ideas are welcome. |
Send message Joined: 29 Aug 05 Posts: 15560 |
I understand you want it to run based on preferences, with the preference of "when idle is more than 3 minutes set, am I correct? You have now installed it as a service, with what preferences? Please list them for me. Have you changed the service itself? If you go Start->Run, type services.msc 9enter), click on BOINC, rightclick, properties, then what is your setting at the Log On tab? It should be Local System Account and the option Allow service to interact with the desktop should be checked if you want to allow the screen saver. |
Send message Joined: 30 Aug 06 Posts: 13 |
It should be Local System Account Gotcha. Perhaps this is where I went wrong. I was using a local account, since the BOINC installer prompts you for a user account to use while installing the service. I'll try that tomorrow and let you know. |
Send message Joined: 30 Aug 06 Posts: 13 |
It should be Local System Account and the option Allow service to interact with the desktop should be checked if you want to allow the screen saver. Darn. Still doesn't work. It continues running until I open BOINC Manager, then it checks the preferences and stops immediately. This means it will run always until someone opens the manager. When I installed, I told it not to start BOINC Manager when each person logs in. I think the magic combination is: 1. Install as a service. 2. Run the service as local system. 3. Start BOINC Manager as a system tray icon whenever anyone logs in. Not sure that will fly with my coworkers. I'll check and see. They won't like the system tray thingy. |
Send message Joined: 30 Aug 06 Posts: 13 |
Not sure that will fly with my coworkers. I'll check and see. They won't like the system tray thingy. Darn. No dice. It has to be 100% transparent to the users. No icons they can click on, processes shut down when they log in. Oh well. Looks like our only option is to leave it as-is and run on a limited timeframe afterhours. Better than nothing I suppose. |
Copyright © 2024 University of California.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License,
Version 1.2 or any later version published by the Free Software Foundation.